Time
S
Nick
Message
01:15 jri joined #dataverse
01:43 pdurbin joined #dataverse
01:43 sivoais_ joined #dataverse
01:43 icarito[m] joined #dataverse
01:44 dzho joined #dataverse
01:44 yoh_ joined #dataverse
01:44 andrewSC joined #dataverse
01:44 JonathanNeal joined #dataverse
01:45 bjonnh joined #dataverse
01:45 candy` joined #dataverse
01:45 bricas joined #dataverse
01:45 cdsp-rmo joined #dataverse
04:15 jri joined #dataverse
07:05 jri joined #dataverse
11:07 poikilotherm joined #dataverse
11:42 donsizemore joined #dataverse
13:12 poikilotherm
Morning guys...
13:12 pdurbin
mornin'
13:13 poikilotherm
pdurbin: thx for pointing out on https://github.com/IQSS/dataverse/issues/5093
13:13 poikilotherm
That made us rethink our approach...
13:13 pdurbin
yeah?
13:13 poikilotherm
As this is relatively new stuff, this wasn't on our radar when we made plans back in 2017 ;-)
13:13 pdurbin
good? :)
13:14 pdurbin
Have you found a link to any docs on the new "reserve" feature for DataCite?
13:14 poikilotherm
We think about giving up on ePIC and just use DOI, no matter the costs.
13:14 poikilotherm
https://support.datacite.org/docs/doi-states
13:14 pdurbin
Ah, thanks. I hadn't looked yet.
13:15 pdurbin
So is this the next thing you want to work on? Or do you have other projects in mind?
13:17 poikilotherm
I think this is worth a try. It might be the much simpler approach compared to the effort to be put into the PID providers. There is a chance we can get the DOIs at a reduced price, too.
13:17 pdurbin
Speaking of reduced prices from DataCite, do you know about https://dataverse.org/global-dataverse-community-consortium ?
13:17 poikilotherm
As the reserved DOI would be recorded within Dataverse, this might be sufficient for our other apps currently in planning. Those actually are kind of persistent and that's all we need.
13:18 poikilotherm
(Or better call'em "draft DOI" as the official docs name them)
13:19 poikilotherm
Yes, I am aware of it, but I didn't have a chance to report it to the guys with the money in their pockets... ;-)
13:20 poikilotherm
And of course we do not have a production grade installation yet :-D
13:22 poikilotherm
While being on that: the consortium is planning to become a member, correct?
13:23 poikilotherm
Are there chances that a member of the consortium might have multiple datacenters with Datacite?
13:23 poikilotherm
(There might be interest at FZJ for this)
13:26 pdurbin
I really don't know. I haven't been very involved. I could point you to some notes and such. There's a contact address on the bottom of that page.
13:28 poikilotherm
Ok, thx. :-)
13:28 poikilotherm
Will ring the bell over there when this gets a bit more concrete...
13:30 pdurbin
poikilotherm: ok, I just talked to sekmiller about https://github.com/IQSS/dataverse/issues/5093 and he said you are welcome to work on it. Want me to move it to Community Dev and give it to you?
13:30 donsizemore joined #dataverse
13:32 poikilotherm
Sure :-)
13:32 poikilotherm
Gimme gimme, gimme an issue after midnight... :-P
13:33 pdurbin
Done! :) You're on a roll. Thanks again for the S3 stuff!
13:33 pdurbin
poikilotherm: oh, the contact is donsizemore's boss by the way
13:33 poikilotherm
You're most welcome :-)
13:33 pdurbin
donsizemore: I'm trying out your branch on EC2. Thanks.
13:34 donsizemore
@pdurbin i was just skimming over your convo =)
13:34 donsizemore
@pdurbin martin didn't want us to publish the credentials and we'd need a decryption password to run the playbook, so... end users can smoke 'em if they got 'em
13:34 poikilotherm
Oh then I'll better try to be polite ;-)
13:35 donsizemore
@poikilotherm no one ever got anywhere by being polite!
13:35 pdurbin
just ask my cats
13:35 poikilotherm
Meouw!
13:36 pdurbin
donsizemore: how interested are you in the EC2 script? I'm thinking about making a ~/.dataverse directory with rc or whatever config files inside ... ~/.dataverse/dataverserc so I can put the DataCite username and password somewhere.
13:38 donsizemore
@pdurbin i'm interested in helping you all test it because we may eventually move to AWS
13:39 donsizemore
@pdurbin also i'm happy to share my test.datacite credentials with you; it's just that martin didn't want them published to github
13:40 donsizemore
@pdurbin i'm also interested in helping whoever in the dataverse community wants to use it (Dataverse community support is even in my job description)
13:41 pdurbin
donsizemore: that's ok, we have some test datacite credentials for harvard dataverse that we share. Moment of truth.
13:41 * pdurbin
clicks
13:41 poikilotherm
Could the Consortium try to get an account for https://test.datacite.org/?
13:41 poikilotherm
I would definitly need something like this for #5093... ;-)
13:45 pdurbin
poikilotherm: I don't think DataCite wants us to share credentials. You should probably email their support address listed at http://guides.dataverse.org/en/4.9.4/installation/config.html#persistent-identifiers-and-publishing-datasets
13:46 pdurbin
"Unlike EZID, DataCite requires that you register for a test account (please contact support
13:47 donsizemore
@poibilotherm correct. Odum has two accounts: test and prod
13:48 pdurbin
donsizemore: your switch_to_datacite branch works! Can I merge it?
13:50 poikilotherm
Most of the code in DOIDataCiteRegisterService seems to be written by Stephen Kraffmiller. Is he in the IRC ? Couldn't find him in the who's who and don't know his GitHub nick...
13:50 donsizemore
@pdurbin please do. sorry to punt and steal pete's shell script, but i experienced frustration with several ansible modules
13:51 poikilotherm
Aaah! sekmiller :-D
13:53 pdurbin
poikilotherm: we share an office. Do you have a question?
13:55 pdurbin
donsizemore: I'm sure he'll be glad you're using his script. It seems to work fine. And it's awesome that you have "Dataverse community support" in your job description. Do you have any interest in working on the ~/.dataverse config file stuff? Making ec2-create-instance.sh aware of it, I mean.
13:56 donsizemore
@pdurbin sure thing. i still have the credentials you sent me...
13:56 pdurbin
donsizemore: cool, can you please do the "create an issue" song and dance?
13:57 pdurbin
The issue is "can't publish using the EC2 script" basically.
14:00 poikilotherm
pdurbin: just commented #5093...
14:02 pdurbin
poikilotherm: yes, thanks. I just talked to Steve about it. We didn't know that supporting draft DOIs involves switching APIs. How do you feel about exploring the new API ?
14:02 poikilotherm
I don't mind, but it means there is a risk about breaking stuff
14:03 poikilotherm
This will definitly need proper integration testing beforehand
14:03 poikilotherm
You don't want me to blow up everybodys publishing :-D
14:03 pdurbin
Absolutely. But I'm sure we could learn something from your exploration. Just like how you've been trying to get Dataverse working on the next LTS releas of Java (Java 11).
14:04 poikilotherm
At least we learned that tests are good and that more of 'em could be usefull... :-D
14:04 pdurbin
:)
14:05 pdurbin
poikilotherm: of course, if there's something else you'd rather work on, that's fine too. Did you see that I asked Jim about his contribution roadmap?
14:06 poikilotherm
Yes I did - but I did not see a response yet, correct?
14:07 poikilotherm
Working on #5093 seems a good idea. At least evaluate what needs to be done and try to approximate the effort.
14:09 pdurbin
poikilotherm: Jim seemed to say it's fine to share it with you: http://irclog.iq.harvard.edu/dataverse/2018-10-03#i_74583
14:09 poikilotherm
IMHO I think working on #4259 (Java 11) will only make sense with more thorough testing of the codebase to be sure these hard to tackle failures don't happen unnoticed in some other place...
14:10 poikilotherm
pdurbin: I read http://irclog.iq.harvard.edu/dataverse/2018-10-03#i_74589 , but maybe I missed the URL ?
14:11 poikilotherm
Who's Sebastian? Seems to be another german community dev?
14:11 pdurbin
poikilotherm: it's called "QDR and Dataverse Coordination" but it says "anyone with the link can edit" so maybe I'll just invite you with "can comment" permission.
14:11 poikilotherm
As qqmeyer quoted him saying "no problem"
14:12 poikilotherm
Sure, carry on :-)
14:12 pdurbin
poikilotherm: ok, please check your email
14:12 pameyer joined #dataverse
14:12 poikilotherm
Thx
14:13 pameyer
@donsizemore http://irclog.iq.harvard.edu/dataverse/2018-10-10#i_75180 - I think you mistyped "efficiently used open source" :)
14:14 pameyer
no reason to revisit the PR; but you can definately use ansible secrets without typing a password
14:14 pdurbin
poikilotherm: Sebastian is the associate director of QDR ( https://www.sebastiankarcher.com ) and promotes Dataverse quite a bit on Twitter and other places. He's great.
14:14 pameyer
dcm has an example of a way to do it in the pre-rpm installation stuff I could dig up if you're interested
14:15 pdurbin
pameyer: rough consensus and running code :)
14:17 poikilotherm
pdurbin: I think you missed something - I can edit the doc...
14:17 pdurbin
bah
14:18 pdurbin
I can't change the permissions.
14:18 poikilotherm
Ok, then I'll just not mess up the hole thing and behave myself
14:19 pameyer
google docs do have edit history
14:19 poikilotherm
Hrhrhr... Anonymous Mouses and other wild animals for the win... :-D
14:19 pdurbin
Thanks. Do you see what I mean about how it helps us understand at a high level what Sebastian and Jim have in mind for Jim to work on in the Dataverse code base over the next year or so?
14:19 poikilotherm
Sure.
14:20 poikilotherm
You would like to see some strategic goals we try to follow with our dataverse
14:20 pdurbin
Do you want me to start a doc like this for you? Or do you prefer the "just in time" model? :)
14:21 poikilotherm
I'll discuss this with my colleagues. Mind if share the link with them so they get the picture?
14:21 pdurbin
Nope. Please share away.
14:21 poikilotherm
Yes Sir! :-)
14:22 pdurbin
And I *think* I just changed it to "anyone can comment" rather than edit.
14:23 poikilotherm
Yey, you did :-)
14:24 poikilotherm
-y+s
14:24 pdurbin
phew
14:28 poikilotherm
OK I just informed my colleagues and we'll see how it goes.
14:28 pdurbin
poikilotherm: cool, again, if you prefer "just in time" and coordinating here or elsewhere that's fine too
14:28 poikilotherm
I told 'em so ;-)
14:29 poikilotherm
IMHO a mixed approach would be a good idea
14:29 pdurbin
Great. Also, since you were on the call yesterday I thought maybe you'd bring up the PID thing to Slava. But you're re-thinking this anyway, it sounds like.
14:29 poikilotherm
Big picture doc, issues assigned and IRC details chatting
14:29 pdurbin
Yep, sounds like a good mix.
14:30 poikilotherm
Yes... Will have a VC with Slava tomorrow and then we'll see how we continue
14:30 pdurbin
awesome
14:30 poikilotherm
I don't know yet if DANS is willing to share their codebase, etc.
14:31 poikilotherm
pdurbin do you or @sekmiller mind to leave a comment on #5093 about the API thing?
14:31 pdurbin
poikilotherm: last commit 29 days ago: https://github.com/DANS-KNAW/dataverse/tree/dans-develop
14:32 poikilotherm
Yeah I know that - but I don't know if the proxy has been integrated or if this is a separate project (which is most probable)
14:32 pdurbin
oh
14:32 pdurbin
yeah, I don't know
14:33 poikilotherm
So let's see what Slava can tell me tomorrow :-)
14:33 pdurbin
I'll bring up the draft/reseved DOI issue at standup in 45 minutes.
14:33 poikilotherm
THX!!
14:33 pdurbin
sure
14:33 pdurbin
always happy to help make contibution easier
14:38 isullivan joined #dataverse
14:38 poikilotherm
_ _ _
14:38 poikilotherm
| | | | | |
14:39 poikilotherm
| |_| |__ __ _ _ __ | | ___ _ ___ _ _
14:39 poikilotherm
| __| '_ \ / _` | '_ \| |/ / | | |/ _ \| | | |
14:39 poikilotherm
| |_| | | | (_| | | | | <| |_| | (_) | |_| |
14:39 poikilotherm
\__|_| |_|\__,_|_| |_|_|\_\\__, |\___/ \__,_|
14:39 poikilotherm
__/ |
14:39 poikilotherm
|___/
14:39 pdurbin
aw, thanks
14:39 poikilotherm
Ah damn, in ASCII this looked a lot better...
14:39 pdurbin
It looks fine in weechat. :)
14:49 poikilotherm
16:50 here - bye for today. Read you tomorrow... :-)
14:51 pdurbin
welcome back isullivan
15:02 donsizemore
@pdurbin so essentially, i'm proposing that the ec2 script make use of a ~/.dataverse/dataverserc file to pass group_vars? just want to be sure i'm doing right
15:04 pdurbin
donsizemore: yeah or whatever makes sense in 2018. ~/.dataverse/config.toml?
15:04 donsizemore
@pdurbin thou hasn't counted the gray hairs in mine beard, hast thee?
15:06 donsizemore
even modern docker wrappers simply call it an env, i'm tempted to do the same
15:13 pdurbin
donsizemore: should we just tell people to put the new environment variables in their .bashrc?
15:16 isullivan
thanks pdurbin! Forgot to setup auto-join for the room last time :)
15:17 donsizemore
@pdurbin a separate env file for dataverse would allow sharing within an organization
15:53 pdurbin
donsizemore: so ~/.dataverse/env? That's fine. Whatever works. :)
15:53 donsizemore
@pdurbin just submitted the issue (and heading for coffee, as one does)
15:58 pdurbin
Thanks! I just left a comment. Much appreciated!
16:14 isullivan joined #dataverse
16:20 donsizemore joined #dataverse
18:52 donsizemore
@pdurbin you know how i push stuff, and tell you to have a ball?
18:54 donsizemore
@pdurbin check out https://github.com/OdumInstitute/dataverse/tree/5162_cant_publish_using_EC2_script/scripts/installer if you will
18:57 pdurbin_m joined #dataverse
18:58 pdurbin_m
donsizemore: I'm on a phone but it looks good. Is there an extra "exit 1" in there?
18:59 donsizemore
@pdurbin_m oh, probably. i'll fix it. lines 45-51 are why i'm going to go for a short walk
19:01 pdurbin_m
yeah that was blowing my mind
19:01 pdurbin_m
as long as it works :)
19:02 pdurbin_m
I'm confused about how -b and -r still work. No longer in getopts.
19:05 pdurbin_m
Over here we document -r and -b: http://guides.dataverse.org/en/4.9.4/developers/deployment.html
19:05 donsizemore
they're in the env file now
19:07 donsizemore
unless i messed up and you want to leave them as runtime flags
19:31 dataverse-user joined #dataverse
19:32 dataverse-user
Hi
19:32 dataverse-user
I want to use the data archiving service, but could locate the registration link
19:44 donsizemore
@pdurbin actually i see more that should've come out depending on how much goes into the env ifle
20:32 pdurbin
shoot, missed him. I'm fine with whatever and happy to tweak the docs on that branch
21:05 pdurbin
I like that the env file can be specified.
21:35 donsizemore joined #dataverse
21:36 donsizemore
@pdurbin i'm back. it's super-easy to dial back the ENV file-shunting, particularly if you'd prefer to pass repo and branch as runtime flags. could also make them override whatever's in either file... just awaiting instruction
21:36 donsizemore
s/instruction/marching\ orders/g
21:44 jri joined #dataverse
22:04 pdurbin
donsizemore: at ease. My daughter is playing cello and I'm strumming along with some chords. The main thing I want is for the docs to match the script.
