Time
S
Nick
Message
01:41
dataverse-user joined #dataverse
02:03
jri joined #dataverse
05:04
jri joined #dataverse
08:01
jri joined #dataverse
12:18
jri joined #dataverse
13:31
ruben48 left #dataverse
16:07
Thalia_UM joined #dataverse
17:00
Thalia_UM1 joined #dataverse
17:01
pdurbin
The community call is about to begin: https://dataverse.org/community-calls
17:02
pdurbin
You're all welcome to call in, of course. bjonnh bret dzho jeffspies______ jhand JonathanNeal karissa larsks mdunlap sivoais Thalia_UM yoh :)
17:37
Thalia_UM1
Good morning ! :)
17:39
Thalia_UM1
I don't good wifi
18:08
andrewSC joined #dataverse
18:13
Thalia_UM1
Philip
18:13
Thalia_UM1
a question?
18:14
pdurbin
Thalia_UM1: hit me
18:15
Thalia_UM1
How can I put my list of values for "Subject" but without having to store the list of values in the database?
18:16
pdurbin
You can't. You have to store them in the database. It's a "controlled vocabulary". Users have to pick from the list of 15 or so subjects.
18:24
Thalia_UM1
https://github.com/IQSS/dataverse/issues/4282
18:25
Thalia_UM1
Yes I know but Is there no way to skip that part?
18:30
pdurbin
No. A controlled vocabulary is a feature. It purposefully restricts the values that a user can enter. That said, for subjects there has been some talk of allowing additional values. See https://groups.google.com/d/msg/dataverse-community/TNRb7hoJd8Q/j8bCRRZNAwAJ
18:36
jgautier joined #dataverse
18:36
pdurbin
Thalia_UM1: I have summoned jgautier to discuss your interest in changing how subjects work in Dataverse. :)
18:37
pdurbin
jgautier: thanks for jumping in here :)
18:37
pdurbin
jgautier: Thalia_UM1 just uploaded additional screenshots to https://github.com/IQSS/dataverse/issues/4282 that you may be interested in.
18:38
jgautier
Thanks for invite. :)
18:39
jgautier
Cool yeah, just saw the screenshots. So I'm guessing that it doesn't matter if someone chooses on of the values in that subject list; the user will always get an error that a subject has to be chosen?
18:39
Thalia_UM1
I was thinking about adding the values but I do not want to store them in the database, the new values.
18:40
Thalia_UM1
yes
18:41
Thalia_UM1
Thanks Philip, Hi jgautier
18:44
jgautier
And the error shows because Dataverse is checking for values stored in the database?
18:45
Thalia_UM1
Yes
18:45
Thalia_UM1
already has 15 values stored in a table in the database
18:46
pdurbin
On the backend, Dataverse is enforcing the controlled vocabulary for subjects. You'd see similar errors if you tried to create a dataset with unsupported subjects via API .
18:46
Thalia_UM1
We chose dataverse because we are working with dataset
18:48
jgautier
Why not store in the database?
18:48
jgautier
I imagine there are performance issues with keeping values in the database up to date?
18:51
Thalia_UM1
The values that I am adding are some web services that we were given to consume, and those web services are updated, the work team wants to add these values but without modifying the database, or touching the development part, only through the XHTML sheets
18:56
jgautier
So I guess the error checking would have to be changed right. Does that sound right?
18:57
jgautier
Maybe so Dataverse is only checking if a subject term has been chosen, and not necessarily one in the database?
18:58
jgautier
Sorry if this is just questions. I'm not a developer, can only really think about this at this level.
18:59
jgautier
But I think I understand the value of storing the terms in the database, although that's not the approach your team would like.
19:01
Thalia_UM1
exactly
19:02
Thalia_UM1
They want me to do that but with the conditions they said, because we only have a month to deliver the project.
19:25
Thalia_UM joined #dataverse
19:30
jgautier
Ah, okay. That's good to know. Thanks! Not sure if it's possible within that time to relax the enforcements pdurbin mentioned.
19:32
pdurbin
A month isn't very long, Thalia_UM . Have you considered using a custom metadata block? You are define it however you wish.
19:33
pdurbin
jgautier: please stop me if a custom metadata block is a bad idea
19:53
jgautier
It seems like a reasonable workaround for now. The only issue I can think of is the usual interoperability one: custom fields of course won't be mapped to fields in the metadata exports
19:54
pdurbin
true
19:54
jgautier
And depositors would still have to choose subject term(s) to publish datasets. Thalia, could you share what the controlled vocabulary is? Is there a website for it?
19:57
pdurbin
jgautier: I think this is it (from yesterday's chat logs): http://catalogs.repositorionacionalcti.mx/webresources/areacono
20:57
Thalia_UM
Yes that is a web service about area of knowledge
22:16
Thalia_UM
I've run out of ideas :-$ Any suggestions, I need to continue to be interoperable with OAI-PMH and export metadata
22:24
jgautier joined #dataverse
22:29
jgautier
Hi again Thalia. Sorry for the delay. I'll try to talk about what else is possible with the developers here at Dataverse. Thanks for your patience :)