-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
myrec$id empty #29
Comments
Hello @oggioniale
The token isn't the same in sandbox and production. In each instance of Zenodo, you have to pick-up a token from your Zenodo account, checking
By creating a blank record with myrec <- zenodo$depositRecord(myrec) In that case this will send your local record to Zenodo, deposit it, and get back the fetched record (with id, doi, etc) into the same R object. You can then publish the record picking up An alternative to create a blank local record to start drafting it is to create directly a blank record in Zenodo, and then you can edit it, and trigger deposit. In that case the record, since deposited early in Zenodo, will have myrec <- zenodo$createEmptyRecord() Apart from that I see that you are from LTER-Italy, it may be interesting that you interact with the french node, related to your work on pushing metadata / manage spatial data (i've seen we exchanged in the past on ows4R) etc I'm in contact with people from "Zone Ateliers RZA" (https://cat.opidor.fr/index.php/E-LTER-France_RZA) pilar of LTER-France. Some data managers from there already use zen4R or other related packages. On my side i'm developing and puts together zen4R, ows4R, etc. This package is named geoflow, which aims is to automate/orchestrate (meta)data publication targeting different systems (eg. Geonetwork/Geoserver for spatial (meta)data, Zenodo, Dataverse, etc). RZA is envisaging to use geoflow to carry out their (meta)data management tasks. This could be of interest of you as well, the only point is that because i developed a lot on geoflow recently, i'm late on documentation, so you will have to be patient to get a complete user manual... But in case you are interested feel free to tell me. Best |
Hi @eblondel, I have used in the past ows4R for some project. The geoflow package is very cool. Is it a package for manage data and curates this in data management sofware that have APIs? In eLTER-RI I'm involved in two H2020 projects for improve the tools for data management and within the CNR-IREA institute we develop a sofware based on GeoNode named GET-IT (the github project) that we propose, in eLTER community, as a country data node. DEIMS-SDR is a repository of the metadata of sites and data, GeoNetwork is a center catalogue of the metadata dataset, B2Share is used for provide DOI to dataset, and finally GET-IT is for the countries that are autonomus for share data. |
Hi @oggioniale geoflow is aimed to be a kind of toolbox for people that want to automate data processings and publication flows targeting one ore software, using APIs, and when available standard protocols. So far i've pushed publication API actions for packages I'm the author, as it eases their integration:
I'm currently looking how a similar publication action could be set-up for Dataverse, which many research institutions used as catalogue, and there is a plan to develop 2 actions related to biodiversity (meta)data:
Recently i've developed and released another package on CRAN to deal with the Open Collaboration Service (OCS) protocol: ocs4R and set-up 2 basic wrappers for NextCloud and OwnCloud. Geoflow is metadata driven. In other words we defined a pivot metadata model, initially inspired from Dublin Core, and expandable to cover more exhaustive metadata standards (such as ISO/OGC or EML). The idea is that people can rationalize their intervention on a single metadata entry point, and trigger multiple actions to target diverse systems (eg Geonetwork/Geoserver for spatial, EML for biodiversity oriented catalogues, general Zenodo/Dataverse for DOI publication). Depending on the actions triggered, these can be inter-related, e.g. you publish some DOI, this DOI can be reflected properly in the ISO/OGC metadata. Vice-versa, you can push different metadata sheets as resources into a Zenodo deposit together with data. The pivot metadata model is defined with an R class model in geoflow, and we provided wrappers to fit profile (user, R developer). For that purpose we set-up a simplified tabular data structure as entry point that could be either CSV, XLSX, Google spreadsheet, or a table in a DBMS. Three kinds of metadata entry points can be set:
Well, I don't want to very verbose. Geoflow is going to expand further in the near future, with some developments for which I have funding opportunities yet, and other not yet (raster support). You can have a look to geoflow, I believe this could be of interest for you, and anyway we can keep in touch. Last but not least, one of my goal is to foster production/publication of metadata not as ultimate goal, but also for to exploit metadata as driver for advanced data exploration. In this purpose i've been developing the OpenFairViewer https://github.com/eblondel/OpenFairViewer, which focus on spatial data, and aims to offer a fully standard ISO/OGC metadata driven map viewer. It relies entirely on OGC CSW for browsing datasets, OGC WxS protocols for data access, and query is enabled by means of ISO 19115 dataset metadata and ISO 19110 structural metadata. This portal is being promoted in some H2020 project as well (which includes a collaboration with Italian CNR-ISTI), and in France some colleagues within the LTER-France network are considering a possible adoption. Its development is tightly bound to the geoflow one with the idea that what you enable in geoflow as spatial data/metadata, is exploitable within OpenFairViewer. |
I'm having a similar problem where my new record My code (left out some lines unrelated to zenodo):
Thank you for your help! |
Hi @PietrH when using the above code on sandbox, I get this:
If i remove the line to set the communities, the R code works, I get an output and |
Hello @eblondel , thanks for looking into this. When I leave my code as is, I get:
With
Which is a possible bug as it reports successful deposition, but doesn't actually deposit? Then after removing the line that adds the communities, I still have the same results. Here is my full terminal printout:
Even if I deposit with just a title and description, I get the same results. Is it possible there's something wrong with my key? If I run
Trying to reach this test record https://sandbox.zenodo.org/record/653087, my key is set to actions and write permissions. I've used it before. I'm on version Zen4R 0.4-3 running in R version 4.0.3 (2020-10-10) -- "Bunny-Wunnies Freak Out" |
Dear eblondel,
I'm testing zen4R for upload some research products for LTER Research Infrastructure the final idea is to propose a ShinyApp.
At this moment I have a problem for upload a records both in the sandobox and in a production one.
In the first cases, when I set the
ZenodoManager
withurl = "http://sandbox.zenodo.org/api"
I receive the answer:
[zen4R][ERROR] ZenodoManager - Error while depositing record: The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required.
In the second case, try to publish the record directly to Zenodo production, the record is deposited
[zen4R][INFO] ZenodoManager - Successful record deposition
but when I try to publish the record I don't understand how to retrive the id of the record deposited.My script for the second case below
How I do it? Thanks a Lot
oggioniale
The text was updated successfully, but these errors were encountered: