TigerData is a comprehensive set of data storage and management tools and services that provides storage capacity, reliability, functionality, and performance to meet the needs of a rapidly changing research landscape and to enable new opportunities for leveraging the power of institutional data.
Apache License 2.0
6
stars
0
forks
source link
Getting the projects create_script task up to date #721
Rejiggered the rake task that we have to generate the Aterm script to create a project in Mediaflux, the code is now in its own class and it is reusable.
I updated the code to produce the script (that we introduced in https://github.com/pulibrary/tiger-data-app/issues/563) to include the new fields in the schema and also added a few extra commands that are only needed then creating the very first project in a Mediaflux instance (i.e. one where not even the root namespace or root collections have been created).
The script creates the collection mimicking the structure that Chuck and Robert are using in production. Notice how the project is under /td-demo-001/tigerdata but its namespace (may16-205NS) is under /td-demo-001/tigerdataNS
I am also displaying the Aterm script in the approval screen. This might be a good way to surface the information to Chuck in a way that is easy to reuse (although not shown in the screenshot, the script also includes the commands to define the collection accumulators and quota):
Rejiggered the rake task that we have to generate the Aterm script to create a project in Mediaflux, the code is now in its own class and it is reusable.
I updated the code to produce the script (that we introduced in https://github.com/pulibrary/tiger-data-app/issues/563) to include the new fields in the schema and also added a few extra commands that are only needed then creating the very first project in a Mediaflux instance (i.e. one where not even the root namespace or root collections have been created).
The script creates the collection mimicking the structure that Chuck and Robert are using in production. Notice how the project is under
/td-demo-001/tigerdatabut its namespace (may16-205NS) is under/td-demo-001/tigerdataNSI am also displaying the Aterm script in the approval screen. This might be a good way to surface the information to Chuck in a way that is easy to reuse (although not shown in the screenshot, the script also includes the commands to define the collection accumulators and quota):