-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GSD Metadata Block #268
Comments
Original Redmine Comment From: Merce: 03/23/14 Merce On Mon, Mar 24, 2014 at 10:22 AM, Eleni Castro (Google Drive) Based on my talks with Janina and the current template they use for GSD, I have put together a preliminary GSD metadata block, which I need your advice on. Based on their particular template use case, there are four issues I'm seeing from moving away from templates:
Please let me know what you think! Thanks! |
Original Redmine Comment Will add this block after beta and review w/ Janina one on one to make sure it will be usable for her group's needs. |
@posixeleni what is the status of this? |
@eaquigley We need to wait till templates are enabled in beta so that Janina can fully test how the GSD and other blocks will work for her group. I already have a draft of the GSD metadata block waiting to be uploaded as soon as templates are ready (any idea what the ETA is for this?). |
Need to move this to later milestone so that templates are fully in place (ability to select which metadata fields are required, recommended or optional see Issue #858 ) for me to implement this metadata block for GSD to test out fully. |
The new |
@kcondon this is the custom metadata block I created for GSD which is now ready for QA. Please let me know if you have any questions! |
@posixeleni you marked many fields as required. Is your expectation that if someone from GSD tries to use the Data Deposit API that they will get an error like "Can't create/update dataset. http://purl.org/dc/terms/ equivalent of required field not found: gsdStudentName"? |
@pdurbin : Correct! Since these are custom fields there is no way this metadata could be sent through a SWORD API. The fields that were marked as required are based on what the User of this custom block has requested and for their use case they would only deposit data via the UI for now until we have our Native API setup to be able to handle custom or more granular metadata elements. |
Tested basic functionality: creating dataset, searching, facets, etc. Also compared to .tsv file. Closing |
Author Name: Eleni Castro (@posixeleni)
Original Redmine Issue: 3682, https://redmine.hmdc.harvard.edu/issues/3682
Original Date: 2014-03-10
Original Assignee: Eleni Castro
Need to put together metadata block(s) for the Graduate School of Design / Architecture & Design.
After meeting w/ Janina we identified the need to possibly create (2) different blocks:
The text was updated successfully, but these errors were encountered: