Hi everyone,
Just a reminder that we have a meeting scheduled tomorrow Thursday February 5 at 2pm ET to discuss the following items in preparation for the final technical report we need to send to Sloan by March 31 (thanks Merce!).
Agenda
* Get updates from Jen/Alex on the checkin of final plugin development changes / bug fixes and if they are available in the latest OJS release.
* Discuss plan to communicate these changes to publishers/journals using/interested in the plugin.
* Have them test these changes and send us feedback (setup testing environment)
* Discuss plan to send subset of original survey to larger group of OJS journals/publishers about their interest in data and data policies.
* Discuss potential paper to submit to Journal of Librarianship and Scholarly Communication (deadline: March 1) http://jlsc-pub.org/jlsc/cfp.html
If you are calling in: the Google Hangout URL is: https://plus.google.com/hangouts/_/calendar/cG9zaXhlbGVuaUBnbWFpbC5jb20.dc9…
Otherwise we meet in K332 at IQSS.
Cheers
Eleni
--
Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science
IQSS, Harvard University
http://www.iq.harvard.edu/people/eleni-castro
We're redesigning Dataverse and want your feedback! Please check out our Beta Site.<http://dataverse-demo.iq.harvard.edu/>
Hi team,
Please fill out this Doodle poll http://doodle.com/858y83bwuttfd8af by EOB Friday November 21st so that I may schedule our next meeting in January (I'm on vacation in sunny California for a week in mid-January) so I hope the dates/times listed are ok with everyone.
I am also including a link to the updated meeting minutes along with some post-meeting action items: https://docs.google.com/document/d/12cXNkGfk9wdtlxx0fThz_lu5-ryaH597iEe10C5…
Post Meeting Action Items
Action
Assigned To
Deadline
Deliverable
Work on final dev updates for plugin
Jen
Nov 30
code in github
Review feedback from responders to follow-up in January
Eleni/Alex
Mid-January
Action plan for follow-ups
Get official to date #’s of journals per publisher we sent the survey to
Alex
Nov 30
spreadsheet
Please feel free to modify, add comments on anything I may have missed or misunderstood.
Thanks,
Eleni
--
Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science
IQSS, Harvard University
http://www.iq.harvard.edu/people/eleni-castro
Hi everyone,
Given the amount of meetings my group has next week, if no one has anything important to discuss in-depth on Monday, I would recommend that we just put our monthly updates in a Google Doc instead of meeting.
So far some of the items we should discuss:
1. Phil: Update on https://github.com/IQSS/dataverse/issues/899. Let Jen know when she can start work on updating plugin.
* When can Jen start work on her end to incorporate these metadata changes?
* Anything not backwards compatible in the API for 4.0 that Jen would need to work on?
2. Survey sent to journals/publishers (3 confirmed responses). Micah: Any metrics from survey monkey?) https://www.surveymonkey.com/s/NTHL7QF Will follow-up with journals to remind them to respond prior to Nov 3 deadline.
If you still think it's important to meet in person please let me know. Otherwise I will distribute a Google Doc on Monday for folks to fill out.
We should also schedule our last November meeting.
Thanks!
Eleni
--
Eleni Castro
Research Coordinator, Data Acquisition and Archiving, Data Science
IQSS, Harvard University
http://www.iq.harvard.edu/people/eleni-castro
We're redesigning Dataverse and want your feedback! Please check out our Beta Site.<http://dataverse-demo.iq.harvard.edu/>
As we discussed yesterday* I believe the way forward for creating
Dataverse 4.0 datasets with more metadata than dcterms is to try
kicking the tires on the new JSON-based "native" API.
Here's how I use it in an integration test:
curl -X POST -H "Content-type:application/json" -d
@scripts/search/data/dataset01-create-new.json
http://localhost:8080/api/dvs/11/datasets/?key=pete
And the JSON looks something like this (truncated but attached and
also available at
https://github.com/IQSS/dataverse/blob/master/scripts/search/data/dataset01…
):
{
"initialVersion": {
"metadataBlocks": {
"citation": {
"fields": [
{
"value": "Rings of Trees and Other Observations",
"typeClass": "primitive",
"multiple": false,
"typeName": "title"
},
{
"value": [
{
"authorName": {
"value": "Tree, Tony",
"typeClass": "primitive",
"multiple": false,
"typeName": "authorName"
},
"authorAffiliation": {
"value": "Trees Inc.",
"typeClass": "primitive",
"multiple": false,
"typeName": "authorAffiliation"
}
}
],
...
I hope this gives a sense of how to use the "native" API. The docs
(for now) are at
https://github.com/IQSS/dataverse/tree/master/scripts/api but we'll
eventually merge them into the API Guide for Dataverse 4.0.
I've developed parts of the native API but this endpoint having to do
with creating and editing datasets I have not. So we can learn
together how best to take advantage of it and I can certainly help
work on any bugs we might find.
The alternative to using the native API is to try to shoehorn more of
our metadata blocks into SWORD but this seems complicated and probably
not the best use of time. For more on that approach, please see this
thread I started on the SWORD mailing list: [sword-app-tech] client
SHOULD add Dublin Core terms to the Atom Entry, MAY add any other
metadata formats or foreign markup -
http://www.mail-archive.com/sword-app-tech@lists.sourceforge.net/msg00384.h…
While I'm excited about the native API I'd like to emphasize that it
is still very much in beta. The place to try it out is
http://dataverse-demo.iq.harvard.edu
I hope this makes what I was saying a little more concrete. Please let
me know if there are any questions!
Phil
p.s. Another potentially useful native API call would be creating
dataverses. This would mean the dataverse wouldn't have to be created
manually for each OJS journal, like it is now under DVN 3.x. See this
script for how we create the root dataverse and some children:
https://github.com/IQSS/dataverse/blob/master/scripts/api/setup-dvs.sh
* https://docs.google.com/document/d/1DCm8rkuUQOlUY1lHqLeHsp26dPd9GwsspLabcCo…
--
Philip Durbin
Software Developer for http://thedata.orghttp://www.iq.harvard.edu/people/philip-durbin