IQSS logo

IRC log for #dataverse, 2019-01-11

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
00:13 isullivan joined #dataverse
08:03 juancorr joined #dataverse
13:26 donsizemore joined #dataverse
13:26 donsizemore @pdurbin i pretty much ported your script for the counter task list. happy to install the counter in /opt or /usr/local or somewhere
13:28 donsizemore @pdurbin also, i'm digging into why the conditional works except as an extra-var...
13:36 pdurbin donsizemore: I guess I have a slight preference for /usr/local over /opt but I'm not sure why. And good morning. :)
13:38 pdurbin I guess this is reflected in the Dataverse Installation Guide. /usr/local is where we suggest that people install Glassfish and Solr.
13:49 pdurbin donsizemore: did I tell you we're meeting with the Counter Processor developers today?
14:07 donsizemore joined #dataverse
15:19 donsizemore joined #dataverse
15:19 donsizemore @pdurbin grrr {"ansible_facts": {"dataverse_counter_enabled": true}
15:21 pdurbin heh. grr?
15:25 donsizemore ec2 is sending it capital True, ansible is interpreting a case-insensitive boolean, then ignoring it
15:25 pdurbin huh, weird
15:25 donsizemore and i'll downgrade the grrr to an rrr
15:25 pdurbin heh. are you interested in joining that meeting? if not, I'm happy to summarize after.
15:50 donsizemore joined #dataverse
15:58 donsizemore @pdurbin will address #35 in the course of #34
15:59 pdurbin donsizemore: thanks, I'm trying to fix it manually right now. Not sure why it's taking me so long.
16:04 pdurbin ok, fixed. phew
16:10 pdurbin hmm, maybe not. I guess I'll reinstall solr
17:12 carlosmcgregor joined #dataverse
17:31 pdurbin carlosmcgregor: hi! Thanks again for https://github.com/IQSS/dataverse/pull/5356 :)
17:32 carlosmcgregor pdurbin: Hello~! Happy I could be of assistance :)
17:33 carlosmcgregor I would like to contribute more on the SwiftDriver
17:33 pdurbin great!
17:34 carlosmcgregor Should I compile a document of what I have in mind? It is mainly doing some code clean up :o
17:35 carlosmcgregor I was also wondering if the SwiftDriver was always intended to have a separate configuration file? If not, I could also work on integrating it to the main config file.
17:36 pdurbin carlosmcgregor: that would be great. And once you're happy with how the document looks (please feel free to drop a link in here), you can paste it into a GitHub issue.
17:37 pdurbin I don't know why there's a separate config file. Or I forgot. :)
17:39 carlosmcgregor :D Please let me know if there is any interest in having everything in a single config file. If so, I can look into it.
17:40 pdurbin carlosmcgregor: we try to work in "small chunks" so please create a separate issue for the config file thing. You can just ask if there's interest in consolidating.
17:41 carlosmcgregor pdurbin: Thank you for the advice! I will do so :)
17:41 pdurbin Sure. Our process can be confusing so it never hurts to jump in here and ask. :)
17:51 donsizemore joined #dataverse
18:02 carlosmcgregor joined #dataverse
18:29 pameyer joined #dataverse
19:23 carlosmcgregor joined #dataverse
19:24 donsizemore joined #dataverse
19:49 Jim_ joined #dataverse
19:51 Jim_ Hey Phil - thanks as usual for the cross-reference to other issues/history!
19:51 pdurbin Jim_: sure! Glad to see you're so interested in external tools. :)
19:53 Jim_ Just wanted to jump in here and make it clear that these issues are things I've done for QDR that can stay custom or be integrated. I.e. they are not intended to be a push, just something that can be taken in or not.
19:55 pdurbin Ok. I'm looking at https://data.qdr.syr.edu but I can't quickly find an example.
19:56 pdurbin You said it was based on MIME type or something.
19:56 Jim_ Not yet deployed to production - probably next week.
19:56 pdurbin Oh. I'll stop looking then. :)
19:57 Jim_ :-)
20:08 pdurbin Jim_: QDR is on 4.9.4. Not bad. Fairly up to date.
20:24 Jim_ Yeah - TDL as well... QDR's 4.9.4 also includes things like the duracloud/chronopolis archiving and sometimes I cherry pick bug fixes back from develop ...
20:26 pdurbin Yeah, the archiving thing just made it's way back to QA a few minutes ago.
20:27 Jim_ TDL will be back to generic when they go to 4.10.1 through they may grab #5426 early.
20:27 Jim_ and thanks on that too - very odd that we don't get the same log conflict error everywhere...
20:28 Jim_ hopefully the excludes fix it.
20:28 pdurbin fingers crossed. Oh, have you played with http://guides.dataverse.org/en/4.10.1/user/dataset-management.html#data-provenance ?
20:28 pameyer @Jim_ I was puzzeled that I didn't get a log conflict error on that branch
20:29 pdurbin I'm asking because https://github.com/IQSS/dataverse/issues/5459 reminds me of upload a PROV-JSON file for a data file.
20:30 Jim_ I've turned it on but haven't done much with provenance... thought about it for hypothesis, but for that the annotations are associated with the dataset, not a specific file...
20:30 pdurbin Oh, I thought you were saying per file.
20:31 Jim_ the annotations are all related to one document - a published pdf at a journal site for example, but that pdf is not in the dataset.
20:31 pdurbin Ok, the plot thickens.
20:33 Jim_ yeah. I had originally implemented the annotations as metadata - no code changes in Dataverse, just some javascript coming in through a custom header page that triggered retrieval as you specified the pdf and group to use.
20:33 pdurbin but that solution ran out of gas?
20:33 Jim_ That was slick, but there was concern that it downplayed annotations relative to datafiles, so we went with making annotations a file.
20:34 pdurbin I see.
20:35 pdurbin Well, I'm glad you're able to put these prototypes into place at least. Long live the custom header. :)
20:36 Jim_ The idea of using javascript to trigger actions during input and to format metadata for viewing seems like a nice pattern in general though for lightweight integration.
20:36 pdurbin Jim_: you should give a talk about this at #dataverse2019 :)
20:38 Jim_ @pameyer - I'm not sure if the errors could appear/disappear based on java version or something else in the environment. From what I saw, it seems like it should be there whenever you have new enough versions of the jars involved...
20:38 Jim_ I might - I need to see what QDR wants to do since they're paying the bills at this point...
20:39 pameyer I was deploying to a fresh container, so that might've been it
20:39 Jim_ what would that change?
20:40 pameyer the only versions of various jars would have come from dataverse.war
20:40 pameyer not entirely sure if/how that would matter though
20:41 Jim_ Ah - OK. I think that should have given you newer jars that should cause the error, but perhaps there's some other version issue (maybe one jar is checking to see if an older version of the other exists?)
20:44 pdurbin Jim_: you're a hired gun for Dataverse. I love it.
20:45 pameyer pdurbin: have you kicked jenkins recently?
20:46 pdurbin I built some docs this morning.
20:46 pdurbin Oh and I ran the phoenix tests a couple times.
20:46 pameyer I'll need to re-run to confirm, but InReviewWorkflowIT.testCur​atorSendsCommentsToAuthor may be unhappy
20:48 pdurbin Hmm. I last ran phoenix tests on the commit before your Solr upgrade was merged. Lemme kick off another run.
20:48 pameyer develop-571ec669e ; but that might be out of date
20:49 pdurbin oh, you're way behind me. there's been a lot of merging this week :)
20:49 pameyer gotcha - I'll update and see if that changes anything
20:52 pameyer and it was a fluke anyway from that commit; 2nd run was fine
21:02 pdurbin pameyer: tests are still passing on the latest in develop: e36173f (your Solr stuff).
21:06 pameyer pdurbin: thanks for checking
21:12 pdurbin sure
21:20 pameyer pdurbin: some days I do dumb things https://github.com/IQSS/dataverse/issues/5460 :(
21:21 pdurbin no worries, approved
21:21 pameyer thanks
21:28 donsizemore joined #dataverse
21:29 donsizemore @pameyer safe to pull the 7.3.1 *.xmls into dataverse-ansible?
21:31 pameyer @donsizemore they're the same xml files as dataverse used for 7.3.0
21:32 pdurbin once pameyer did a `git rm` of the old xmls it was more clear that they're the same
21:32 pdurbin since git just shows a move
21:32 pameyer content addressable storage is nice that way
21:34 pdurbin :)
21:34 pdurbin on that note, I'm off, have a good weekend everybody, stay warm
21:34 pdurbin left #dataverse
21:34 donsizemore i still want versioned conf files for each release... whether they're duplicate
21:35 pameyer the first 7.3.1 PR failed to put them into dvinstall.zip
21:35 pameyer but if I'm understanding you right; they're versioned
21:43 donsizemore =)

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.