As soon I finish prototyping my smart DAQ with swarm capabilities I intend to take a peak at the dataverse source code to propose some improvements in regards to live data acquisition and open science ... Almost there
Here's the newest smart DAQ with SWARM capabilities
Available on my public GitHub profile to anyone use
@poikilotherm dataverse.files.directory is only used for temporary files these days, correct? I'm asking because I ran across target/classes/META-INF/microprofile-config.properties:dataverse.files.directory=/tmp/dataverse
poikilotherm (CEST,UTC+2)
No it's not!
There is a list in the docs where this stuff is used
(I asked myself the same thing when going for Mpconfig)
This is a sane default for most installations and development
Btw this directory is the default which had been present in the code before as well
Pooch looks promissing, it would be great if we could download all the files, metadata and permissions associated with a said dataset and upload them to a different dataverse instance.
We asked our CERT team to do a blackbox security check of our dataverse installation, they found two vulnerabilities, one regarding the jQuery UI 1.13.0 version (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31160) and another regarding the absence of Anti-CSRF tokens. Should we create an issue
Dataverse also has an issue with the session cookie being sent in cleartext, we tried using a session cookie from a coleague in my browser and I was able to impersonate him.
Dataverse also has an issue with the session cookie being sent in cleartext, we tried using a session cookie from a coleague in my browser and I was able to impersonate him.
You can skip this one, it was a misunderstanding, as fot the others, we have sent an email regarding the issues.
*
Dataverse also has an issue with the session cookie being sent in cleartext, we tried using a session cookie from a coleague in my browser and I was able to impersonate him.
You can skip this one, it was a misunderstanding, as for the others, we have sent an email regarding the issues.
Hello everyone I want to change the way to display the metadata citation in the subject field. I need the field to be displayed in URL format. I've been thinking about editing the tsv.
Hello, I am trying to add a new metadatablock (for local contexts labels). I could add my tsv with the api endpoint. However whenever I want to save a dataset with some fields of that metadataset, I get: "The metadata could not be updated. If you believe this is an error, please contact Root Support for assistance.". This is the tsv file that I started: https://github.com/RIDAGOP-IDS-Toolkit/tklabel/blob/main/localcontexts_dv_metadatablock.tsv
Hello, I am trying to add a new metadatablock (for local contexts labels). I could add my tsv with the api endpoint. However whenever I want to save a dataset with some fields of that metadataset, I get: "The metadata could not be updated. If you believe this is an error, please contact Root Support for assistance.". This is the tsv file that I started: https://github.com/RIDAGOP-IDS-Toolkit/tklabel/blob/main/localcontexts_dv_metadatablock.tsv
Actually, I just notice, that with the latest version of the tsv, the metadata of a dataset DOES update, even tho it still shows the same error message
poikilotherm (CEST,UTC+2)
Did you adapt your Solr schema as described in the Metadata Customization Guide?
Did you adapt your Solr schema as described in the Metadata Customization Guide?
after updating schema, it cannot reload. I am getting a 500, and in the response trace I see (down in the trace): "...Duplicate field definition for 'accessToSources' [[[accessToSources{type=text_en,properties=indexed,tokenized,stored,useDocValuesAsStored,uninvertible}]]] and [[[accessToSources{type=text_en,properties=indexed,tokenized,stored,useDocValuesAsStored,uninvertible}]]]\n" the field "accessToSou" is not from me. its the very first field in the file.
sure! here you go: The RIDAGOP (Indigenous data sovereignty) toolkit (https://toolkit.ridagop.net/) allows developers to create generic data-management processes, connect them to data-repository systems. This demonstrates 2 processes; adding Local Contexts Labels to datasets and how to create a customizable data access application processes.
Did you adapt your Solr schema as described in the Metadata Customization Guide?
ok. manually adding them worked. and saving the dataset goes through ! :) I might write a python script to the update in the future. not sure why the update-fields didnt work
* ok. manually adding them worked. and saving the dataset goes through ! :) I might write a python script to do the update in the future. not sure why the update-fields didnt work
