Author (email) addresses

57 views
Skip to first unread message

Leif Longva

unread,
Feb 7, 2014, 8:21:34 AM2/7/14
to dataverse...@googlegroups.com

Hi, we consider starting to use Dataverse. I have looked at the DDI 2.5 schema. Now, we would like to include contact information for each author of a study or dataset. I find the “affiliation” attribution under the “AuthEnty” element. But I do not find an “address” attribution or something like that. So how may we enter (email) address information, related to each individual author in a study?

 

Yours,

Leif Longva
UiT Arctic University of Norway

Philip Durbin

unread,
Feb 7, 2014, 10:46:40 AM2/7/14
to dataverse...@googlegroups.com
Hi Leif,

This is a great suggestion but it will require some research on our
part so I created a ticket to track it:
https://redmine.hmdc.harvard.edu/issues/3538

Here's what the ticket says:

"Metadata: email addresses per author instead of one email address per dataset

Currently, in 3.x, you can only have one contact per study. That
contact can have an email address. Authors cannot have email
addresses.

For 4.0, Merce asked me to create a ticket and have Eleni try to
figure out if DataCite or other metadata standards have the concept of
per-author email addresses. See also "Contact Email" under "DV
Attributes 4.0" under the "Additional General Metadata" tab at the
"T1: General Metadata" doc:
https://docs.google.com/spreadsheet/ccc?key=0AjeLxEN77UZodHJSRHlzdTBVcXcwWTRVa3Bfdm91ZWc&usp=sharing

Once we decide we can support this or not, we should, of course, reply
to the original Google Group thread."

Thanks,

Phil
> --
> You received this message because you are subscribed to the Google Groups
> "Dataverse Users Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dataverse-commu...@googlegroups.com.
> To post to this group, send email to dataverse...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dataverse-community/ca579c5d-d91f-47b9-9043-f1d2b450b0bc%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--
Philip Durbin
Software Developer for http://thedata.org
http://www.iq.harvard.edu/people/philip-durbin

Eleni Castro

unread,
Feb 11, 2014, 9:39:27 AM2/11/14
to dataverse...@googlegroups.com, philip...@harvard.edu
Hi Leif,

Thanks for bringing this question to our attention.

I did some digging and found out that DDI allows for repeatable instances of the Contact field but at the moment our system only permits one contact per dataset. For 4.0 (tracked in this ticket: https://redmine.hmdc.harvard.edu/issues/3538) we will change the cardinality of this element to allow for multiple email addresses (contacts) instead of just one per dataset. With this addition multiple authors can include their contact information. Would this modification suit your institution's needs?

Best regards,
Eleni

Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science (http://thedata.org)
IQSS, Harvard University
http://www.iq.harvard.edu/people/eleni-castro 

Stephen Marks

unread,
Feb 11, 2014, 4:40:35 PM2/11/14
to dataverse...@googlegroups.com, philip...@harvard.edu
Hey all--

Just putting this out there because it's kind of related: would there be interest in doing a big old revamp of the Study Description metadata to bring it into full DDI compliance at some point? (Or at least compliance with Section 2?) We have librarians we could dedicate to such a task. ;)

Steve

Eleni Castro

unread,
Feb 12, 2014, 9:05:32 AM2/12/14
to dataverse...@googlegroups.com, philip...@harvard.edu
Hi Steve,

Great timing on this question.

We are in the midst of some big changes for 4.0, (http://thedata.org/blog/major-dataverse-release-coming-spring-2014) and included in that is looking at how we handle metadata (moving up from DDI 2.1 to 2.5), expanding to support domain-specific metadata (social sciences, astrophysics and biomedical (for now)), support mapping/exporting to other general metadata schemas like DataCite 3.0, etc.

I'll create a new post so we can start a discussion specifically on how our users believe we should handle metadata in Dataverse going forward. In that post I will be sharing plans (tables) we are working on for 4.0 metadata.

Thanks so much for offering your group's assistance on this!

More to come later today,
Eleni

-- 

Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science

Reply all
Reply to author
Forward
0 new messages