| Time |
S |
Nick |
Message |
| 17:51 |
|
|
jwhitney joined #dvn |
| 18:07 |
|
pdurbin |
jwhitney: hi |
| 18:08 |
|
jwhitney |
pdurbin: hello |
| 18:09 |
|
pdurbin |
jwhitney: did I tell you I'm exposing a list of database IDs for files now? |
| 18:09 |
|
jwhitney |
pdurbin: no, but that's great! |
| 18:11 |
|
pdurbin |
jwhitney: https://sword:sword localhost:8181/dvn/api/data-deposit/v1/swordv2/collection/dataverse/sword is the URL I'm using right now for this, but I might need to move it somewhere else |
| 18:11 |
|
jwhitney |
pdurbin: ok |
| 18:11 |
|
pdurbin |
jwhitney: oh, something else. that "v1" is new... |
| 18:12 |
|
jwhitney |
pdurbin: ok. Catching up on chat logs, etc., after a couple of days of course work |
| 18:12 |
|
pdurbin |
the whole "v1" will have enough for OJS... later versions will do more... |
| 18:13 |
|
pdurbin |
jwhitney: the readme at https://github.com/dvn/swordpoc/tree/master/dvn_client is new too. not sure if you've seen it |
| 18:14 |
|
jwhitney |
pdurbin: no, will walk through it this afternoon |
| 18:14 |
|
pdurbin |
jwhitney: cool. I tried it out myself from the Vagrant VM. works great |
| 18:15 |
|
jwhitney |
awesome. |
| 18:15 |
|
pdurbin |
jwhitney: this is new too: [Dataverse Network - Suggestion #3208] Allow the Data Deposit API to use API keys - https://redmine.hmdc.harvard.edu/issues/3208 |
| 18:16 |
|
pdurbin |
jwhitney: won't be in v1 but I wanted to make you aware of it |
| 18:16 |
|
jwhitney |
pdurbin: great, thanks |
| 18:17 |
|
pdurbin |
jwhitney: the last thing (for now) that's on my minds is next steps... |
| 18:17 |
|
pdurbin |
Eleni wants the ability to delete a study |
| 18:17 |
|
pdurbin |
so I've been refactoring the code to make that easier |
| 18:17 |
|
pdurbin |
I also want to add the ability to update the metadata of a study (title, author, etc). |
| 18:18 |
|
pdurbin |
jwhitney: if there's something else you want sooner than these, please let me know |
| 18:19 |
|
pdurbin |
jwhitney: also... we talked briefly about metadata for files... we *do* have metadata for files on the DVN side... 1. filename 2. description (optional) 3. category (optional) |
| 18:19 |
|
jwhitney |
pdurbin: ok, from the OJS side, can we assume a study should be deleted after all associated files have been deleted? |
| 18:19 |
|
jwhitney |
pdurbin: perhaps that's getting ahead of things. |
| 18:19 |
|
pdurbin |
jwhitney: hmm, I wouldn't assume that necessarily.. |
| 18:20 |
|
pdurbin |
I've been thinking of it more as... if a study is deleted, all of its files get deleted too |
| 18:20 |
|
jwhitney |
pdurbin: ah, ok |
| 18:20 |
|
pdurbin |
but we can hash this all out some more |
| 18:20 |
|
jwhitney |
pdurbin: for sure. |
| 18:21 |
|
pdurbin |
jwhitney: so those 3 pieces of metadata for files... you want me to expose that too? and give you the ability to update the metadata? (filename, description, category) |
| 18:25 |
|
jwhitney |
pdurbin: yes, I think so. |
| 18:26 |
|
jwhitney |
pdurbin: I've been working on the assumption that OJS should reflect what's in DVN, rather than the other way around |
| 18:26 |
|
pdurbin |
hmm, interesting |
| 18:26 |
|
pdurbin |
I've been thinking that OJS is more "authoritative" :) |
| 18:26 |
|
jwhitney |
pdurbin: ha. |
| 18:26 |
|
pdurbin |
since OJS is pushing data to DVN |
| 18:27 |
|
jwhitney |
pdurbin: yep, that's fair. |
| 18:28 |
|
jwhitney |
pdurbin: but once in DVN, should edits made in DVN take precedence over those made through OJS? |
| 18:28 |
|
pdurbin |
jwhitney: excellent question :) |
| 18:30 |
|
pdurbin |
with a Google Doc, who ever edits last "wins" so to speak |
| 18:30 |
|
jwhitney |
pdurbin: that's what I've been thinking, which is why files & file metadata from your side seem necessary |
| 18:31 |
|
pdurbin |
jwhitney: right. because before making an edit you'd probably like to check the current state |
| 18:31 |
|
jwhitney |
pdurbin: yes, exactly |
| 18:32 |
|
pdurbin |
makes sense |
| 19:02 |
|
pdurbin |
jwhitney: I'm thinking about how to document the DVN SWORDv2 API.. what do you think of how this looks? http://developer.runkeeper.com/healthgraph/example-api-calls |
| 19:04 |
|
jwhitney |
pdurbin: clear, easy to follow |
| 19:17 |
|
pdurbin |
jwhitney: yeah |
| 19:18 |
|
pdurbin |
because the SWORD spec is a bit too generic... someone wanting to deposit data into DVN via SWORD is going to need to know the DVN-specific implementation details |
| 19:20 |
|
pdurbin |
jwhitney: I guess https://dev.twitter.com/docs/api/1.1 looks fine too but it's long... there's a lot more you can do with Twitter's API |
| 19:33 |
|
|
sbmarks left #dvn |
