eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/contributors
The following people contributed to the development of the Lagotto software:. Original developer of the Article-Level Metrics application. Gerad Suyderhoud and Visnu Pitiyanuvath). Software developer at PLOS. Software developer at PLOS. Software developer at DataCite. Software developer at Cottage Labs. Software developer at PKP. Software developer at eLife. Software developer at Mutually Human. Software developer at Crossref.
eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/deployment
Installs all required software and code. From then on all code updates - including database migrations - are much easier as we no longer need to install Ruby, Nginx, MySQL, etc.:. On local installations (e.g. using Virtualbox) update all code with. Run databases migrations if necessary with. Bundle exec rake db:migrate. If necessary update the installed Ruby gems via. And then restart the Rails application server with. On remote installations (e.g. using AWS) use the Capistrano. File in the local Lagotto...
eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/roadmap
51 Bug fixes May 2016. The focus of this release is on bug fixes. Lagotto 5.0 introduced a lot of breaking changes, and some of them will only be obvious after running production systems for a while. Please use the Github issue tracker. 52 Upgrade path for Lagotto 4.x June 2016. This release will provide an upgrade path for Lagotto 4.x users. Import of data from other Lagotto 5.x instances.
eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/setup
Lagotto supports the following user roles:. API user - only API key. Contributor - add content via the deposit API. Staff - read-only access to admin area. Admin - full access to admin area. Lagotto supports the following forms of authentication:. Authentication via username/password is not supported. Third-party authentication is configured in. Variable. Configuration settings for ORCID, CAS, Github and JWT are also provided via ENV variables. Configuring Agents and Sources. Timeout (default 30 sec).
schema.datacite.org
DataCite Schema
http://schema.datacite.org/meta/kernel-3.1/index.html
DataCite Metadata Schema 3.1. Released 16 Oct 2014. DataCite Metadata Working Group. (2014). DataCite Metadata Schema for the Publication and Citation of Research Data. Version 3.1. DataCite e.V. http:/ doi.org/10.5438/0011. DataCite Metadata Working Group. (2014). DataCite Metadata Schema for the Publication and Citation of Research Data. Version 3.1. DataCite e.V. http:/ doi.org/10.5438/0010. Changes in this version include:. New affiliation attribute for Creator and Contributor.
eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/deposits
The deposits API provides a common way to import data into Lagotto. It was introduced in Lagotto 5.0. Import of data via rake task, as in previous Lagotto versions, is no longer supported in Lagotto 5.0. Action does an update if the. Describes target for the deposit, either. Add or update relation. Add or update contribution. Add or update publisher. Unique identifier (usually a UUID) for the agent responsible for the deposit. Required. A valid Lagotto API key associated with a. Is in the same format as.
schema.datacite.org
DataCite Schema
http://schema.datacite.org/archive/kernel-2.0/index.html
This version is only provided for archival purposes. It is no longer usable with the DataCite MDS. DataCite Metadata Schema 2.0. Released 24 Jan 2011. DataCite Metadata Working Group. (2011). DataCite Metadata Schema for the Publication and Citation of Research Data. Version 2.0. DataCite e.V. http:/ doi.org/10.5438/0002.
eventdata.datacite.org
DataCite Event Data
https://eventdata.datacite.org/docs/api
Version 7 of the API was released April 11, 2016 (Lagotto 5.0). API calls start with. API versioning is done via the request header, e.g. Accept: application/json; version=7. And currently defaults to. Previous API versions are no longer supported because of breaking changes in the data model. The v7 API requires the API key in the header in the format. Authorization: Token token=API KEY. All API endpoints are described in the live API documentation. The most important ones are:. And number of results (.
SOCIAL ENGAGEMENT