Time
S
Nick
Message
00:46
djbrooke joined #dataverse
01:17
djbrooke joined #dataverse
02:59
djbrooke
hey Alexandre-FGV, Dataverse can export in a few different formats. Can you explain a bit more what you mean by metadata schema here?
08:33
jri joined #dataverse
08:34
jri_ joined #dataverse
09:09
Youssef_Ouahalou joined #dataverse
09:32
pkiraly joined #dataverse
10:01
pkiraly joined #dataverse
10:02
Youssef_Ouahalou
Hello :)
10:11
Youssef_Ouahalou
I had a problem when setting up a production datacite account, everything works but when I create a dataset the dynamic link does not work do you have a solution please?
10:12
Youssef_Ouahalou
for exemple :https://dataverse.arch.be/dataset.xhtml?persistentId=doi:10.34934/DVN/D0QGDB the link with "https://doi.org ......" is don't working
10:13
Youssef_Ouahalou
How should we configure ": shoulders"?
10:24
Youssef_Ouahalou joined #dataverse
10:26
pkiraly joined #dataverse
10:46
pkiraly joined #dataverse
11:17
donsizemore joined #dataverse
12:10
Kelly_Ayala joined #dataverse
12:12
Youssef_Ouahalou joined #dataverse
12:19
donsizemore
@Youssef_Ouahalou I'll ask our archivists for a smarter answer, but in Odum's case we simply preserved our shoulder from the previous EZ-ID system. The EZID "test" shoulder used FK2 so you'll see that used fairly often. My personal guess is that it's arbitrary.
12:26
Youssef_Ouahalou
@donsizemore okay thank you so much :)
12:45
poikilotherm
Youssef_Ouahalou: I love your 404 page :-D
12:50
poikilotherm
Youssef_Ouahalou: I looked at the code to see where this might fall apart
12:53
poikilotherm
I see a very subtle, but maybe important difference
12:54
poikilotherm
When you use the DOI link, you are redirected twice
12:54
poikilotherm
From https://doi.org/10.34934/DVN/D0QGDB to https://dataverse.arch.be/citation?persistentId=doi:10.34934/DVN/D0QGDB to http://dataverse.arch.be/dataset.xhtml?persistentId=doi:10.34934/DVN/D0QGDB
12:54
poikilotherm
Please watch out for the http:// instead of https:// for the last redirect
12:55
poikilotherm
When entering via HTTPS , you will access the dataset, when accessing via HTTP , sth seems to go wrong. This smells like a HTTPS rewrite issue.
12:56
poikilotherm
On one hand, this seems like a bug, as you should be redirected to HTTPS , not via HTTP .
12:57
poikilotherm
On the other hand, this also is likely to be a problem with your reverse proxy.
12:58
poikilotherm
About that :Shoulder setting... Many people take the advantage of adding the repo name in there. But this is up to you, of course.
13:07
Kelly_Ayala
Hi everyone. I'm starting with dataverse and I'm used to technologies like Dspace and OJS. In both I can visualize the metadata schema (like Dublin Core) used in my installation. I would like to known if I can and how I can know what metadata schema was choosed by the dev when he installed (he doesn't work here anymore).
13:07
Kelly_Ayala62 joined #dataverse
13:08
Kelly_Ayala62 left #dataverse
13:09
Kelly-Ayala joined #dataverse
13:20
poikilotherm
Hey Kelly-Ayala
13:20
poikilotherm
Welcome to the show.
13:21
poikilotherm
The easiest way forward for this would be to go to a Dataverse and take a look at its configuration
13:23
poikilotherm
When you head for editing your Dataverse, you can see all available metadata schemas in the "General information" tab.
13:23
poikilotherm
(Just choose it from the dropdown)
13:24
poikilotherm
The available schemas are instance global, so it doesn't matter in which Dataverse you take a look
13:26
Kelly-Ayala
Thank you@
13:26
Kelly-Ayala
*!
13:27
Kelly-Ayala
I'm trying here
13:31
Kelly-Ayala
so, I'm looking at General information page, and in my point of view they are types of metadata and not the schema used. I already read the manual and i believe it's not clear to me yet
13:31
Kelly-Ayala
like, the guide has this information: •Citation Metadata: compliant with DDI Lite, DDI 2.5 Codebook, DataCite 3.1, and Dublin Core’s DCMI Metadata Terms (see .tsv version). Language field uses ISO 639-1 controlled vocabulary. •Geospatial Metadata: compliant with DDI Lite, DDI 2.5 Codebook, DataCite, and Dublin Core (see .tsv version). Country / Nation field uses ISO 3166-1 controlled vocabulary. •Social Science & Humanities Metadat
13:32
Kelly-Ayala
How can I know my dataverse is DataCite 3.1 and not Dublin Core's DCMI? Or it's all of then? Don't know if I make my self clear
13:43
djbrooke joined #dataverse
14:07
Youssef_Ouahalou
@poikilotherm thanks;), I added a line of code from there: https: //notfound.org/fr
14:08
Youssef_Ouahalou
How can I fix the problem? because I do not understand how how this redirect problem and occurred
14:09
poikilotherm
Youssef_Ouahalou: the redirect problem seems to have a root cause in the code/Glassfish not adding the correct protocol.
14:11
Youssef_Ouahalou
is this file ? /usr/local/glassfish4/glassfish/domains/domain1/config/domain.xml ?
14:12
poikilotherm
Is your reverse proxy under your control?
14:13
Youssef_Ouahalou
No, I do not think so
14:15
poikilotherm
Do you actually use a reverse proxy?
14:16
poikilotherm
Or did you configure Glassfish itself to listen for port 443 and SSL traffic?
14:17
Youssef_Ouahalou
It was not me who configured this so I don't know :(
14:45
djbrooke
Hi Kelly-Ayala, Dataverse stores metadata in JSON format but can expose it in a few different ways through exports. For an example of this, go to https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/L20LOT and click the "metadata" tab and then the export metadata drop down to see the options available
15:02
Kelly-Ayala
@djbrooke thanks a lot, I fully understood now
15:03
djbrooke
Kelly-Ayala: great, we're happy to answer other questions as you have them
15:07
donsizemore joined #dataverse
15:12
pkiraly joined #dataverse
18:39
donsizemore joined #dataverse
18:49
jri joined #dataverse
23:05
djbrooke joined #dataverse
23:46
djbrooke joined #dataverse