Technical details
The DeepGreen Prototype is a platform that enables publishers to send notifications to corresponding instiutions so that the data can be published in Open Access repositories. At its simplest, a notification is a package providing details of one article only. The notification may also include the article text either embedded in the metadata or in associated binary files, for example PDF or WORD documents and graphics files.
In order to use the DeepGreen Prototype both publishers and institutions must have completed the sign-up process which results in the creation of a DeepGreen account. This is used to configure and administer the DeepGreen Prototype settings that are necessary for connection.
Matching of notifications to an institutional repository is a key function. This is done using a set of matching criteria that each participating institution provides via their administration screen. Each notification is compared with these criteria and those that match are flagged for routing to that institution's repository. Criteria may include any of the following:
- Institution name variants (reflecting different names by which an institution is known)
- Email or web domain names associated with the institution
- ORCIDs of authors
- Email addresses of authors.
To ensure compliance with the licensing terms of the Alliance licenses the DeepGreen Router has access to information provided by the Elektronische Zeitschriftenbibliothek (EZB). These will be included in the accounts and in the metadata.
Information for Institutions
Content coming soon.
Information for Publishers
Notifications
Notifications are a combination of JSON metadata and packaged binary content (such as XML metadata files and fulltext PDFs, etc). Each notfication contains one publication. The system accepts these notifications into the index, then they are matched against repositories based on information each institution gives DeepGreen regarding the notifications they are interested in (based on information such as affiliation, author identifiers, etc). The matched notifications are then made available via the API for repositories to consume and ingest into their own archives.