Time
S
Nick
Message
00:21 axfelix joined #dataverse
01:16 axfelix joined #dataverse
03:23 axfelix joined #dataverse
03:26 garnett joined #dataverse
04:33 garnett joined #dataverse
04:36 garnett joined #dataverse
08:07 jri joined #dataverse
09:46 icenerveshatter joined #dataverse
09:48 icenerveshatter left #dataverse
10:29 jri joined #dataverse
11:31 xvx joined #dataverse
13:31 bmckinney joined #dataverse
14:04 pdurbin
bmckinney: morning. Last night I read this and now I'm feeling a little guilty for encouraging you to hang out in here: Is group chat making you sweat? — Signal v. Noise — Medium - https://m.signalvnoise.com/is-group-chat-making-you-sweat-744659addf7d #.qe7qe1jrl
14:05 pdurbin
but I think you and I have enough discipline to not let this channel distract us
14:11 bmckinney
pdurbin: thanks, nice article. yeah, i sometimes have to look away...
14:12 pdurbin
It's easy enough for me to minimize the window. :)
14:12 pdurbin
I'm working on shib docs for https://github.com/IQSS/dataverse/issues/2953 right now which doesn't require much concentration. :)
14:20 pdurbin
anyway, it's a good read. many valid points
14:52 pameyer joined #dataverse
15:28 bmckinney
pdurbin: just ran my dataverse playbook on a brand new laptop (osx 10.11.3) - took less than 10 minutes, everything is up and running
15:29 pdurbin
bmckinney: I'm interested in the "destroy" side of things. Something to replace https://github.com/IQSS/dataverse/blob/v4.2.4/scripts/database/homebrew/delete-all followed by https://github.com/IQSS/dataverse/blob/v4.2.4/scripts/database/homebrew/rebuild-and-test
15:30 bmckinney
pdurbin: right, i'll chip away at those via new tags. for example, i added a pg-init tag that will reset the db yesterday
15:31 pdurbin
bmckinney: ok. maybe I'll wait until you have parity with what I currently do
15:31 pdurbin
I just ran those scripts this morning. :)
15:32 pdurbin
delete-all and rebuild... I mean
15:33 bmckinney
well, if they work no reason necessarily to recast them as ansible tags
15:35 pdurbin
sure. maybe my first step will be to determine if they are compatible with the ansible way
15:45 pdurbin
once I make a pull request out of https://github.com/IQSS/dataverse/issues/2939 I'm planning on setting up my new laptop
16:20 axfelix joined #dataverse
16:38 jri_ joined #dataverse
17:50 xvx joined #dataverse
18:02 xvx_ joined #dataverse
18:31 axfelix joined #dataverse
18:39 pdurbin
pameyer: I just saw Eleni's email. https://github.com/IQSS/dataverse/blob/v4.2.4/scripts/deploy/phoenix.dataverse.org/post includes a call to https://github.com/IQSS/dataverse/blob/v4.2.4/scripts/search/tests/grant-authusers-add-on-root which may be of interest
18:39 pameyer
pdurbin: I just saw that as well
18:39 pameyer
thanks for the pointers
18:40 pdurbin
sure. the point is that you can script the equivalent of the toggle in the gui. I think the toggle includes three options
18:40 pdurbin
ah. 4 options, actually
18:41 pdurbin
these are the four options: http://guides.dataverse.org/en/4.2.4/_images/dv3.png
18:45 pameyer
maybe a naive question - but can I list users with the API ?
18:45 pdurbin
if you build from https://github.com/IQSS/dataverse/tree/2939-shib you can :)
18:45 pameyer
or GUI - but that seems to have less user management stuff
18:46 pdurbin
... using a method called "listAuthenticatedUsersExperimental()" :)
18:47 pdurbin
pameyer: I was thinking about documenting it just now but decided to just write that the user id comes from the ``authenticateduser`` database table
18:47 pdurbin
pameyer: what would you want the "list users" API call to return?
18:48 pameyer
authenticateduser.useridentifier would be what I'd expect that call to return
18:49 pameyer
whether or not that's the best way to design an API is open to debate of course
18:49 pdurbin
ok. and the id I guess
18:49 pdurbin
I'm also showing the provider (builtin vs shib).
18:49 pameyer
is the integer id something that's used elsewhere?
18:51 pdurbin
yeah, the integer id is used in solr "permission" documents. and the new convert-from-shib-to-builtin method I wrote as part of https://github.com/IQSS/dataverse/issues/2915
18:55 pdurbin
this is the script I use to look at solr permissions docs: https://github.com/IQSS/dataverse/blob/v4.2.4/scripts/search/query
18:58 pameyer
thanks pdurbin
18:58 pdurbin
sure
19:26 bencomp joined #dataverse
19:30 axfelix joined #dataverse
20:18 pdurbin
pameyer: "orchestra" - https://github.com/IQSS/gentb-site/issues/8
20:19 pameyer
orchestra does many things
20:19 pdurbin
heh
20:29 axfelix joined #dataverse
20:42 axfelix joined #dataverse
21:08 pdurbin
pameyer: so you're thinking you'd like me to make that "list users" API call real? Documented and everything?
21:14 pdurbin
bencomp: I'm proofreading what I wrote for https://github.com/IQSS/dataverse/issues/2953 before pushing if you have anything you want me to add. Shib docs.
21:18 pameyer
pdurbin: maybe; not sure how much of the problem is lack of farmiliarity on my end with how dv handles user management type stuff
21:19 axfelix joined #dataverse
21:20 pdurbin
pameyer: in general, the philosophy is that users should be able to do most things themselves
21:25 equigley joined #dataverse
21:26 equigley
hi @pameyer. @pdurbin brought your listing users via API comment to my attention. question: what is the problem you are trying to solve by listing users? is it to get a high level overview of who is in the system? seeing the permissions? seeing the breakdown of from which departments they are from? or something else.
21:28 pameyer
hi @equigley. The immediate problem I was trying to solve was "what's the username of a user I'd like to promote to superuser?". I'm not sure how general of a problem that it is; it's more that it seemed counter-intuitive that the API had functions to change user properties without being able to query them.
21:29 pameyer
Something related that just occurred to me - I know there's a lot of consideration for use cases, but is an operations user (aka - someone driving a dataverse install) considered a user?
21:30 equigley joined #dataverse
21:30 sivoais joined #dataverse
21:33 equigley
@pameyer answer to your second question first: we use superuser to be the same as the person driving the install. additionally, we use the superuser role for all of our support team so they can see the whole installation via the UI (or through the API if they felt like it).
21:33 equigley
i'm not super familiar with the API so i can't speak to being able to change user proprieties without being able to query them.
21:34 equigley
we've had requests from other installations to be able to have a big list in the UI of all users and what roles they have so if you are +1'ing that, i'll add you in as another requestor.
21:35 pdurbin
pameyer: you're right. it's unintutive. you want a list before you start operating on users
21:35 pameyer
@equigley - feel free to add me as another requestor for that.
21:36 equigley
will do @pameyer. we can also talk in person about this tomorrow after the Big Data Design Meeting. i find it easier to chat in person rather than via email or chatrooms
21:36 pameyer
pdurbin: I try not to assume that just because something's unintuitive to me that it's generally unintuitive; but if I'm not the only one then it might be reasonable
21:36 pameyer
equigley: sounds good
21:40 equigley
excellent @pameyer!
21:40 equigley
and now i'm going to back out of this chatroom and pretend like i was never here :)
21:40 pameyer
fair enough :) - see you tomorrow
21:43 axfelix joined #dataverse
23:53 axfelix joined #dataverse
