You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an Administrator I need the ability to import additional production projects so I can keep the front end up to date with what is currently in Mediaflux.
the will be a script in mediaflux that creates CSV formatted data, keeping the format the same as the current rake task asset,path,creatorDomain,creatorUser,createdOn,quota,store,projectDirectory,title,description,dataSponsor,dataManager,dataUser,department,projectID
The administrator will click a button "Import Mediaflux Projects" on the Administration dashboard, which will run the script and then import the csv data into the server4. If a DOI exists nothing gets created or updated
if a typo gets put into the DOI an email get sent to the Dev team to update the DOI
Acceptance criteria
The mediaflux script is created (RC) tigerdata.project.export.generate
The script is installed in the developer docker container
The script is installed on td-meta1 & td-metalib1 (RC)
The script is installed on production mediaflux (RC)
The current Rake task code is move into a service object that can be called from the UI or the rake task
There is a mediaflux command to run the script and parse the results to return the CSV data
There is a UI button "Import Mediaflux Projects" on the administrator dashboard that cause the script to be run and the service object to be called
We test the button with Research Computing to make sure it is behaving as desired in td-meta1 & td-metalib1
Concrete example
Implementation notes, if any
The text was updated successfully, but these errors were encountered:
User story
As an Administrator I need the ability to import additional production projects so I can keep the front end up to date with what is currently in Mediaflux.
asset,path,creatorDomain,creatorUser,createdOn,quota,store,projectDirectory,title,description,dataSponsor,dataManager,dataUser,department,projectID
Acceptance criteria
tigerdata.project.export.generate
Concrete example
Implementation notes, if any
The text was updated successfully, but these errors were encountered: