Do we want to go with actual sticky labels or just normal printer paper for the system?

1. User scans samples to go to beamtime.
2. Software uploads relevant info to PASS SAF (may need SAF number here).

Should we take the repo public?

Some sphinx API doc goodness would be nice.

Need functionality for turning QR codes back into UUIDs.

User runs

a = sample_from_QR()
xrun(a, 0)

Search database based on QR codes.

1. Turn QR into UUIDs
2. Search db by UUID

1. User scans all samples going to BNL.
2. Software creates beamtime spreadsheet with sample info
3. User fills in extra info
4. User goes to beamline to run experiment.

We need to make a bunch of UUIDs and convert them to QRs
Critical questions

1. What is the relationship between UUID length and QR size?
2. What is the appropriate size for the QR code?

It seems that the QR starts with the letter e then that e is missing from the excel sheet.

Have config file so we don't need to ask for ssh info every time.

It might be easier to work with the QR sheets if the ordering is:

|123|456|789|
|123|456|789|
|123|456|789|
|abc|efg|hij|
.
.
.

That way we can cut vertically for each set then cut horizontally in bulk giving strips of a single number where the users don't need to cut the label to get a single QR.

The config file needs some docs.

CircleCI to start (if possible) since we are currently running private.

• Text wrapping for keys
• Special required keys
• Format cells to strings
• Units/suggestions
• Drop down menus

Create sample spreadsheet from list of QRs.

1. Get list of QRs from user
2. Check that all QRs have no sample associated with them.
3. Generate spreadsheet with QR column and other required columns
4. Upload spreadsheet to sampledb

Produce a command line interface for this. (See entry points?)

Put docs on the web

Proposed workflow

Workflow 1: Obtaining Samples

1. BG student gets samples in mail
2. BG student affixes QR code to sample/sample bag
3. BG student scans into DB running in add_sample mode
4. BG student fill out resulting spreadsheet with sample info

Workflow 2: Getting ready for BT

1. BG student is going to Beamtime
2. BG student scans all the samples going to beamtime in to DB in beamtime mode
3. Software puts out beamtime sample spreadsheet
4. BG student fills out any additional info
5. BG student takes spreadsheet to BNL for loading into xpdAcq

If we succeed in publishing samples we should say so.

Usually when we are taking data it gets put into a databroker. The databroker takes care of storing large data sets. However, we may get data with the samples (eg XRD patterns taken on a lab source) which is not in the databroker. How should we handle this?

The way I see this there are two options (although there may be more):

1. Sidewinder the data into the databroker (although we are missing tons of metadata, some of it critical (x-ray wavelength?))
2. Put the data into filestore and hand the sample database the tokens. On retrieval we can open up the data.

It would be nice to have a requirements file (or a few, run doc and test)

It might be nice to have some quickstart info for users to start using the system.

See: https://regro.github.io/regolith-docs/collections/courses.html