Hi Science Drupalistas,
On Wednesday we'll build on last month's DOI discussion, with "DOIs for Drupal Documents" - an exciting project proposal in our Citation track presented by Janine Aquino of UCAR and the Earth Observing Laboratory (EOL).
We're also gearing up for the Summer Lab this July at the ESIPFed conference in Asilomar CA (http://commons.esipfed.org/2015SummerMeeting). If you have any great ideas for speakers or a session proposal of your own - now's the time to bring them to the table! Any ideas, input or feedback is very much appreciated.
Join us Wednesday 22nd April at 3pm ET (further info below) - see you there! David
DOIs for Drupal Documents
In Janine's words: "EOL has a need to create and display DOIs for citable web-hosted documentation. I will share some of the examples that have surfaced at EOL that document this need. Please come prepared to share your examples.
It will be helpful for me to treat this task as a formal project within the ESIP-Drupal working group. If we have clear objectives, deliverables, and timelines, I can more easily obtain permission to work on the project. Would this be helpful to others, or is this overkill?
Finally, I will share some of the ideas for solutions that we have been discussing, and would like us to do some brainstorming on possible next steps, so come prepared with your ideas."
Summer Lab
We'll discuss the results of our survey on our focus area for the Summer Lab, 3 small funding awards to attend, and the creation of different "tracks" as a focus for webinars, Lab seminars and code sprint efforts.
Bring along your ideas for format, topics, speakers or even your own session or lightning talk proposals, and we'll build these into our planning for the event in July.
Meeting Info
Date: Wednesday, April 22, 2015 3:00 pm, Eastern Time
URL: https://esipfed.webex.com/esipfed/j.php?MTID=mbc6d930fdfb5019177e4849c83...
Audio: use webex's built in audio, or dial in on:
* 1-877-668-4493 Call-in toll-free number (US/Canada)
* 1-650-479-3208 Call-in toll number (US/Canada)
* 1-650-479-3208 Call-in toll number (US/Canada)
Access code: 231 367 82
Comments
Follow up discussion on DOIs for Drupal docs - input needed!
Hi all,
Last week's session on DOIs for Drupal documents, lead by Janine Aquino, brought forward the discussion in a number of interesting ways - identifying key functionality we'd need but also a number of sticking points, particularly around how DOIs are used for web documents in contrast to a more traditional, static publishing model.
You can access the call notes in the Google Doc at: https://docs.google.com/document/d/1rwPaKUaSoXT_nDq8aID-rVkPNUHNsOuDrdPq...
I've summarized the key discussion points below, along with my impression of the state of the discussion. If you have thoughts, corrections, or can fill in any gaps, please comment below!
We'll also be posting out a survey covering some of these points. Look out for that in the next few days.
Thanks! David
Spoke with our DOI expert
This is Susan Haberer from NASA Langley. I didn't speak up much during the telecon as I am not our DOI expert. I spoke with our DOI expert, her comments are below. They start with a "-".
Our main site is https://eosweb.larc.nasa.gov
She references our CERES project in a few places. Hope this adds to the conversation!
Are DOIs or URLs better identifiers for scientific web documents?
Current thoughts: DOIs, as they're persistent, whereas URLs can change
–When Web URLs change, DOIs will need to be updated. The only thing that can not change with a DOI is the DOI Name itself (e.g. 10.5067/Terra/CERES/EBAF-TOA_L3.002.8) The additional information can, however, be updated.
Is the Drupal page to be used as the "document of record" for the DOI, or is that stored on some other system?
Current thoughts: intent of the project is for Drupal to serve as the master copy of the content for DOI purposes
Which web content should have a DOI?
Current thoughts: no official guidelines, it's up to institutions or individuals to decide, either on a per-content type or per-page basis
When there's a new revision of a web page, should we generate a new DOI or a new DOI revision? Are there any official guidelines for DOI revisions?
Current thoughts: undecided - some institutions use revisions, others issue new DOIs; need more information on best practices, or which approach is most widely used
When a page is revised, should the new DOI or DOI revision point to the URL of a revision in Drupal (ie. stored in the database), or to an independent snapshot of that page (eg. as a PDF)?- I am pretty sure this was addressed above
Current thoughts: undecided
Which DOI service is most widely used and provides sufficient access via API (ie. to create and update DOIs)? - NASA also uses EZID but I don't know that it matters – I do know that a spreadsheet is sent to the ESDIS DOI leads and they are able to extract the information from the spreadsheet and automatically update, reserve, and register DOIs
Current thoughts: unknown - NCAR uses EZID, which does have an API (http://ezid.cdlib.org/doc/apidoc.html), but it's not clear how widely used this service is amongst other institutions
DOI expert feedback
Hi Susan,
These are all great points. I will work them in to the documents I am pulling together so they can be considered as part of the module work.
Janine
Drupal DOI module: Scope survey
Hi all,
I just created a survey to help define what we all need from a Drupal DOI module. Please fill it out at:
https://docs.google.com/forms/d/13RdLZWDNRjNRxc7U-m8tkeAcRlN-7mtc1LV7Ec1...
and if you are aware of anyone else who would be interested, feel free to forward it along. I will go over results at the June 24 telecon.
Thanks!