Skip to content
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

Closed
eaquigley opened this issue Jul 9, 2014 · 10 comments
Closed

GSD Metadata Block #268

eaquigley opened this issue Jul 9, 2014 · 10 comments
Assignees
Labels

Comments

@eaquigley
Copy link
Contributor


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:

  1. Architecture & Design (in general) - see attached SAHARA document (metadata for architectural images). Janina is also looking up a "materials" metadata document for me. Will be meeting with Harvard Libraries group to see if we should have an "Arts & Architecture" block or if they need to be separate.
  2. Specifically for the Graduate School of Design based off the templates they currently use in 3.6.2. The templates however have fields with controlled vocabulary that changes every Semester (ex. Course Name, Faculty Name, Semester Year) so we need to keep that in mind. Keeping track of the GSD block here: https://docs.google.com/spreadsheet/ccc?key=0AjeLxEN77UZodFZSUmtJYzBna0hwLThBbi1sSDN2X3c&usp=sharing
@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Eleni Castro (@posixeleni)
Original Date: 2014-03-25T19:39:04Z


From: Merce: 03/23/14
This looks good, I think it will be easier to review it briefly all together if we can.

Merce

On Mon, Mar 24, 2014 at 10:22 AM, Eleni Castro (Google Drive)
Architecture / GSD Specific Metadata Blocks
Hi Merce, Gustavo and Sonia,

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:

  1. They are using selective pieces of the Social Science block (geography-related) but they wouldn't want the whole social science block to display (see attached spreadsheet). For searching/browsing it doesn't make sense to recreate the same fields as would be available in the Social Science block, right?

  2. They want a Keywords (Tags) field that would have a controlled vocabulary for GSD (but also allow users to add new terms).

  3. They are not currently using the Author field in 3.6.2 and instead created their own "Student Name" field, which will have to change since we require "Author" for 4.0. Sonia, do you foresee we would receive pushback on this? They could still have a Student Name field in their block but they'd HAVE to fill out the Author one as well.

  4. Most of their fields that have a controlled vocabulary would need to be updated (add/drop/change) every semester. Based on our planned database model would this be ok? Since it is Semester based Gustavo came up with a possible solution for this if we support multiple levels of controlled vocabulary (hierarchical).

Please let me know what you think!

Thanks!
Eleni

@eaquigley
Copy link
Contributor Author


Original Redmine Comment
Author Name: Eleni Castro (@posixeleni)
Original Date: 2014-04-21T05:55:29Z


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.

@eaquigley eaquigley modified the milestones: Dataverse 4.0: Beta 4, Dataverse 4.0: In Review Jul 15, 2014
@eaquigley
Copy link
Contributor Author

@posixeleni what is the status of this?

@posixeleni
Copy link
Contributor

@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?).

@posixeleni
Copy link
Contributor

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.

posixeleni added a commit that referenced this issue Oct 20, 2014
For fieldType changes see #614.
These will require us to manually change in the DB and then have Phil
do a schema.xml change.

For new GSD Block addition see: #268
@pdurbin
Copy link
Member

pdurbin commented Oct 20, 2014

The new customGSD.tsv block is in the Solr schema.xml as of 90bfda4

@posixeleni
Copy link
Contributor

@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!

@pdurbin
Copy link
Member

pdurbin commented Oct 23, 2014

@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"?

@posixeleni
Copy link
Contributor

@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.

@kcondon
Copy link
Contributor

kcondon commented Oct 31, 2014

Tested basic functionality: creating dataset, searching, facets, etc. Also compared to .tsv file.
Looks good, a couple minor issues opened as separate tickets.

Closing

@kcondon kcondon closed this as completed Oct 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants