we have a file-based assay that includes a custom upload.html page. This HTML page is configured for the normal import pathway that most users will see. However, I need to import a lot of legacy data. I wrote a second upload page with code to take this data as one big excel file, then pivot it into one big batch with a series of runs grouped using subjectId (aka one run per subject).

I developed this second HTML page by replacing our normal upload.html page. while this new page is probably a one-time use, it wouldnt hurt to keep it around and to have it somewhere I could access via the web. Is there anywhere in the module where I can put this file such that the normal upload.html page is preserved, yet I would still be able to link directly to this new page should I ever need to?

I moved the custom upload.html file to the views directory of the module. However, when I load this page I get the error 'LABKEY.page is undefined' - which I assume happens b/c this view isnt being loaded by the assay code and does not have the assay-specific objects. I could probably use the API to get the same information, but I thought I'd ask if there's anything quicker first.

Thanks for the help.