[ ] New migrations: add 2 tables to the database: manifest (directories, objectIDs) , objects( objectID: {licence, keywords, contact....})
[x] New routes (web.php): add get(/objects) to read manifest, add get(/objects{objectid}) to read object specific info
[ ] Add interface for user to describe their run
[ ] Add "publish/share" button: update manifest table, query user and update object table, protect run,
[ ] Use minIDs for public job identifiers
To enable the following behavior
1) a user runs the tool
2) the user likes what they made and wants to share it
3) they click the "publish/share" button
4) they are redirected to a form/popup/page where they can provide the query response to get(/objects/{objectID}) where the object ID is the name of their run directory
5) [internal] check to confirm that their response is valid
6) [internal] add their object to the manifest table
7) [internal] add their response to the object table
8)[interal] copy their run directory to a protected run directory (make sure the data is protected too
9) return a message to the user indicating successful publication with a link to their protected analysis page
To enable the following behavior 1) a user runs the tool 2) the user likes what they made and wants to share it 3) they click the "publish/share" button 4) they are redirected to a form/popup/page where they can provide the query response to get(/objects/{objectID}) where the object ID is the name of their run directory 5) [internal] check to confirm that their response is valid 6) [internal] add their object to the manifest table 7) [internal] add their response to the object table 8)[interal] copy their run directory to a protected run directory (make sure the data is protected too 9) return a message to the user indicating successful publication with a link to their protected analysis page