We need knowledge acquisition regarding the upload of files and the batch creation of records and their record_identifier subresources
So that a implementation path can be ticketed
File types supported:
-- tsv
-- sdf
-- xlsx
-- json
Headers (for tsv and xlsx) and tags (from sdf files) should be able to be mapped to identifier types.
The user experience can be either
-- an upload of the file, forget it, view the status of the upload later. (status bars, asynchronous, no loss of data or partial load)
-- upload the file and within less than 10 minutes (with a status bar) for a 1M record file the user can navigate away with all records minted
Acceptance Criteria:
Review the expectations of the functionality as described in the epic: #269
Teach everyone on the team about the options
hausman-gdit
commented
3 years ago
We need knowledge acquisition regarding the upload of files and the batch creation of records and their record_identifier subresources So that a implementation path can be ticketed
File types supported: -- tsv -- sdf -- xlsx -- json Headers (for tsv and xlsx) and tags (from sdf files) should be able to be mapped to identifier types. The user experience can be either -- an upload of the file, forget it, view the status of the upload later. (status bars, asynchronous, no loss of data or partial load) -- upload the file and within less than 10 minutes (with a status bar) for a 1M record file the user can navigate away with all records minted
Acceptance Criteria: Review the expectations of the functionality as described in the epic: #269 Teach everyone on the team about the options