search

IQSS / dataverse

Open source research data repository software
http://dataverse.org
Other
885 stars 495 forks source link

Metadata: Review which ones should be system required on Edit Dataverse page #967

Closed eaquigley closed 10 years ago

eaquigley commented 10 years ago

Based of DataCite schema. For compound fields, should a user be able to select Required or Optional at the parent level or child level? Could you also review whether metadata fields should be textboxes, checkboxes, radio buttons, etc. Should depositor and deposit date be required? Hidden? What does this mean? How do the system requirement fields impact the Data Deposit API?

posixeleni commented 10 years ago

Will also review to make sure all the tsv files display correctly in the UI. For example will fix in the Citation tsv file the fieldType for "Kind of Data" to not display as textbox but as text

posixeleni commented 10 years ago

Out of the 6 Mandatory DataCite Fields only 3 of them are in the citation.tsv the other three are system generated by Dataverse. The rest are strongly recommended by DataCite or are part of a parent child compound field.

Only Notes is not listed as Mandatory or recommended by DataCite but this was something Gary had asked for.

mercecrosas commented 10 years ago

Eleni,

do you mean "System Generated Fields Not in Citation Block"? I think you meant "in citation block", right?

Mercè Crosas, Ph.D. Director of Data Science, IQSS Harvard University http://iq.harvard.edu/merce-crosas

On Mon, Oct 20, 2014 at 1:09 PM, Eleni Castro notifications@github.com wrote:

Out of the 6 Mandatory DataCite Fields only 3 of them are in the Citation Block the other three are system generated by Dataverse. The rest are strongly recommended by DataCite or are part of a parent child compound field.

Only Notes is not listed as Mandatory or recommended by DataCite but this was something Gary had asked for.

-

Depositor and Deposit Date are initially system generated to make it easier for users not to have to enter this information but we give them the option to edit this afterwards. DataCite strongly recommends these two.

The two system requirement fields: Contact and Subject (with a dataverse controlled vocabulary) affect the Data Deposit API since there are no Dublin Core field that are comparable to be able to describe these elements successfully via the API. However, a solution for this one would be to document this in the API Guide and make it clear that users can have these selected at the Dataverse level for contact of the dataset and Subject(s) of the Dataset.

Reply to this email directly or view it on GitHub https://github.com/IQSS/dataverse/issues/967#issuecomment-59799430.

posixeleni commented 10 years ago

@mcrosas sorry meant to say in Citation block!

pdurbin commented 10 years ago

Subject (with a dataverse controlled vocabulary)

I'm just leaving a note here to remind us that #769 is about adding a subject field at the dataverse level.

posixeleni commented 10 years ago

@eaquigley @sekmiller @scolapasta this is related to #858 I have put together a table (See comment above: https://github.com/IQSS/dataverse/issues/967#issuecomment-59799430) to show what required metadata fields are mentioned by DataCite. We will need to make sure that for compound fields just because the parent is selected does not mean that ALL the children of the parent are REQUIRED by default. Let me know if you need anything else from me to get #858 shipped for Beta 8

eaquigley commented 10 years ago

@kcondon & @esotiri can you confirm the metadata fields marked as required in this spreadsheet match with what is going on in Dataverse?

kcondon commented 10 years ago

Yes, required fields in citation block match what's in the spreadsheet.

Closing