Time
S
Nick
Message
03:41 axfelix joined #dataverse
04:29 andrewSC joined #dataverse
05:23 axfelix joined #dataverse
05:53 bjonnh joined #dataverse
08:41 jri joined #dataverse
10:29 djbrooke joined #dataverse
13:02 jri joined #dataverse
13:22 donsizemore joined #dataverse
13:54 iamtimmo
pdurbin: big trouble in DOI land. I couldn't migrate datasets with well-formed DOIs in them. Wondering if we'll be able to even configure our DOI authority. :-(
13:56 pdurbin
iamtimmo: I just took a peek at https://archive.data.jhu.edu/dvn/ and I'm seeing global IDs like "hdl:TEST/10067".
13:57 iamtimmo
yeah, those are the globalIDs, which I had hoped to change during the migration. but loading any ddi with a doi in the IDNo causes barfing and failure.
13:58 iamtimmo
lots like this: server.log_2017-01-20T06-09-58:Caused by: java.lang.IllegalArgumentException: Failed to parse identifier: doi:10.7281/T1J10120
13:59 iamtimmo
the dv4 instance is not visible to you, pdurbin
13:59 pdurbin
that's fine, I believe you :)
14:00 pdurbin
It looks like you wrote a bit about your migration plan here: Transitioning from Handles to DOIs during migration - Google Groups - https://groups.google.com/forum/#!msg/dataverse-migration-wg/6jokT6uPtHM/3gCl8J2eBgAJ
14:00 iamtimmo
pdurbin: The problem seems to be here... https://github.com/IQSS/dataverse/blob/3a753cacb52eef009ae96fd89cf5ee1d193a8a9c/src/main/java/edu/harvard/iq/dataverse/GlobalId.java#L100
14:02 iamtimmo
our DOI prefix does not include a slash, so this code blocks us using them.
14:05 pdurbin
iamtimmo: yes, it's trivial for me to write a failing test. Can you please open a GitHub issue with "doi:10.7281/T1J10120" in it?
14:05 iamtimmo
sure
14:05 pdurbin
thanks
14:11 pdurbin
this commit is related: https://github.com/IQSS/dataverse/commit/7ba9194
14:24 iamtimmo
pdurbin: https://github.com/IQSS/dataverse/issues/3583
14:24 pdurbin
iamtimmo: thanks!
14:26 iamtimmo
pdurbin: Any idea when that commit is going to make it into a release?
14:26 pdurbin
oh, that was an old commit
14:27 iamtimmo
okay. maybe we'll be able to add the DOIs back in after I upgrade to 4.6, then
14:29 iamtimmo
I wonder if I could do a clean install, upgrade to 4.6, and then do the migration. Without breaking anything.
14:30 pdurbin
iamtimmo: maybe but I'm not the expert on migration. You should probably follow up on the migration mailing list thread above and email support
14:31 iamtimmo
pdurbs: Yeah, I'm already composing the message.
14:31 pdurbin
perfect
14:50 pdurbin
iamtimmo: thanks for posting this: highest version of DV that supports migration scripts (DOI problems w/ 4.3.1) - Google Groups - https://groups.google.com/forum/#!msg/dataverse-migration-wg/bFYugiKVvd8/IpsLxRB6AwAJ
14:51 pdurbin
iamtimmo: when you get that IllegalArgumentException... is that on Dataverse 4.3.1?
14:53 iamtimmo
pdurbin: yes
14:54 iamtimmo
have to drop off. I'll be back for a while in an hour or so.
14:54 iamtimmo
thanks for the support, pdurbin!
14:55 pdurbin
sure thing
15:11 pameyer joined #dataverse
15:13 donsizemore joined #dataverse
15:19 pameyer
pdurbin: iamtimmo's comments reminded me of some of the work bmckinney did about migrating datasets with existing DOIs. May or may not be helpful, but might be worth a look
15:20 djbrooke joined #dataverse
15:20 pdurbin
pameyer: is there a link I should look at?
15:20 pameyer
let me check
15:21 pameyer
https://github.com/sbgrid/sbgrid-dataverse/tree/feature/doi-import for a starting point
15:21 djbrooke joined #dataverse
15:22 pdurbin
yeah, it's related but won't be a solution for Tim (JSON vs. XML )
15:23 pameyer
gotcha
15:23 pdurbin
djbrooke: mornin'. If you could read the IRC logs from today it would be much appreciated.
15:24 djbrooke
Got it, thanks!
15:39 andrewSC joined #dataverse
15:48 steeleworthy joined #dataverse
16:00 donsizemore joined #dataverse
16:03 donsizemore
@djbrooke Odum had no trouble with identifiers, but all of our datasets had handles or DOIs-with-separators.
16:16 djbrooke
Thanks @donsizemore!
16:42 jri joined #dataverse
17:16 donsizemore joined #dataverse
17:44 donsizemore joined #dataverse
17:47 djbrooke joined #dataverse
18:48 donsizemore joined #dataverse
18:53 andrewSC joined #dataverse
18:56 djbrooke joined #dataverse
18:59 djbrooke joined #dataverse
19:01 djbrooke joined #dataverse
19:35 donsizemore joined #dataverse
19:59 djbrooke joined #dataverse
20:10 pameyer
DvObjects are both Datasets and Dataverses, right?
20:11 pameyer
aka - if an API is supposed to return DvObjects, I should expect to see both?
20:12 pameyer
^ disregard - problem was on my end
20:12 pdurbin
disregarding :)
20:13 pameyer
;)
20:13 pameyer
… but for future reference of anybody searching the logs, the answer is yes
20:13 pdurbin
technically, DataFile also inherits from DvObject
20:15 pameyer
right
20:15 pameyer
the context was api/dataverses/$id/contents thought
20:15 pameyer
the *invisible* context….
20:20 pdurbin
ok
21:37 axfelix joined #dataverse
21:45 pameyer
has anyone run into a case where metadata fields don't show up in browsing after a reindex?
21:45 pdurbin
Do they show up via API ?
21:46 pameyer
good question - checking now
21:48 pameyer
*tried* to check - which API ?
21:48 pameyer
api/metadatablocks/$identifier doesn't list facitable
21:49 pameyer
but according to api/dataverses/$id/facets , no
21:49 pameyer
user error again?
21:50 pdurbin
an API like this: https://dataverse.harvard.edu/api/datasets/:persistentId?persistentId=doi:10.7910/DVN/RNXA2A
21:50 pdurbin
I assume you mean metadata fields in a dataset you created.
21:50 pameyer
correct
21:52 pdurbin
If you're talking about metadata fields that aren't in the citation metadata block, I wonder if you're suffering from https://github.com/IQSS/dataverse/issues/756
21:53 pameyer
these are in the citation; and now showing up in the API
21:54 pameyer
user error again….
21:54 pameyer
:<
21:55 pameyer
pdurbin: thanks for the troubleshooting help
22:01 pdurbin
oh sure
22:55 djbrooke joined #dataverse
23:34 djbrooke joined #dataverse
23:59 iamtimmo joined #dataverse
