Page History

...

Vision for new implementations

Staff authentication and authorization

H4. Customer Authentication and Authorization

Project management

• not clear if redmine is the right solution, but it has its place now. would need similar functionality, probably with better integration with other components.
• What we like about redmine-  A really nice way to see the history of a particular plate of DNA or project:
  • Project summary: enzyme to use, contact information, expected sample number, comments for data analysis
  • Project workflow where we can check off status and note if something did not go as expected
  • Links that cross-reference.  I link all costs to plates so I know what has been paid for.  We also can link redo plates with the original preps.
  • Upload submission sheet, quantification, experion files (.pdf)
  • Note payment status
  • Track optimization results and R&D
• Would be great if we could check in samples are received when we print the barcode and automatically notify sender that they have arrived.

...

• 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.
• 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

Billing

• if ordering is handled through LSCLC LIMS, invoicing will be easier (less manual) but this may not be necessary
• My thoughts right now are centering around whether or not it makes sense to have customers actually place orders through the LSCLC LIMS system. I would like to avoid it if possible.
• Theresa's comments on GBS billing issues

Benefits:
1) Order is collected along with payment information with one set of credentials by the customer.

Disadvantage:
1) We would be asking bioteam to code within our LSCLC LIMS base - I don't think this is the best way to go
2) order information would have to be migrated to minilims(or custom) GBS LIMS.

Possible mitigation:
1) Configure minilims to use the LSCLC LIMS for authentication.  This will require a development meeting with my group and bioteam to determine feasibility

• 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
• support for credit cards is required
• perhaps we should talk with Brianne because low volume billing might be doable with minlims capability and some low impact manual process by the office staff (unlike the high volume LSCLC invoicing). It keeps GBS separate completely from LSCLC (not sure if that is good bad or indifference)
• if not using LSCLC for billing, not so strong of a need to tie authentication/authorization from minilims to LSCLC LIMS.
• if not using LSCLC, credit card processing NOT possible

Misc operations

• Configure new adapter plate configurations
  • self service interface/upload?