“ We may or may not need to reflect as we are faced with 1) different editions (plus next/prev; disambiguate at level) , 2) different methods within edition (plus next/prev; disambiguate) , 3) different issues of the method (plus next/prev; disambiguate at level) . My initial thoughts are that we look to have version pages for edition/method/issue, and maybe they contain the prev/next, and we just drop down to the specific components, with upward navigation. Otherwise maybe we need to customise the header template if we wnat a more complex navigation. ”

“ So it sounds as the edition has a specified set of methods, though the issue version of the method can be of any age, and pretty much independent of the data of production of the edition. So WS is trying to capture a work at the time of its production, with any reflection of the real time world is coincidental, not through requirement (ie. we are not the real time reference site by design) . ”

“ You could just create an Index for each data sheet, which given the files are already uploaded would be quicker, you would then just need to add a conventional on each index rather than building a complex page list. ”