*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
IGD-GBS MiniLIMS Proposal v1_2.doc
action items
- Rob Elshire and IGD generate minimum distribution information standard
- standard created. need documentation from Rob/Charlotte
- Theresa defines details of billing dashboard page
- IGD create lists of pages (data objects and dashboards?)
- define "page"? I thought you might have meant data objects, but I think not. if you mean "user interface" isn't it better to define in terms of functionality and use case? implementation of "pages". I guess I'm not totally positive what you need from us.
- Charlotte detail spec for workflow
- IGD detailed sample submission spec
- IGD define roles and authorization levels for each page
- James define APIs for billing and ordering integration with CLC LIMS
- not a pre-requisite for contract and project launch.
...
- no changes required at this time ???
- possibly change SOP to record that data was released
- Our current scope does not include any changes to data distribution, which is currently done manually via dropbox or hard drive.
- detailed specification for the information/format of data and metadata distribution:
- Rob Elshire will be producing a standard for information (In my mind I think of it like MIAME or MIAPE standards).
there may be different definitions for different classes of customers- customers that receive only sequence data and metadata about panel in the form of a "Key File".
- customers for whom the facility has produced genotypes. they may or may not also want the sequence data.
- Rob Elshire will be producing a standard for information (In my mind I think of it like MIAME or MIAPE standards).
- build a distribution mechanism that defines the contents of an archive file that can be accessed via web link, including programmatically (curl or wget) and suitable notification
- could be modelled on the distribution that our sequencing facility produces
- note use of "cntrl" parameter which is a keycode so that anyone with that link that includes that parameter can download the file without explicit authentication. Since it could be brute forced it nags at me a little bit, but it does make programmatic downloads easier and security by obscurity should be sufficient enough for this purpose.
- CLC will provide storage available to minilims from which files can be served. whoever runs the pipeline analysis will assemble archive and place in filesystem
data distribution spec:
- could be modelled on the distribution that our sequencing facility produces
Billing
- minilims will provide a "dashboard" page
- Theresa will define the information on this page. I'm not sure what "level" of view she needs. per project, per sample, per order?
- minilims can make a RESTful query to CLC LIMS/Billing System and return existing invoice information per project (or sample or order)
- minilims page will provide functionality to open an existing invoice (in new window?)
- minilims page will provide functionality to submit an HTTP GET or POST to RESTful interface in the CLC LIMS/Billing System that will
- provide an order or invoice number (available to minilims at time order is placed), a line item(s) description, price, quantity
- service will create an invoice and return a reference to the invoice so that it can be opened from minilims
...