Ansible scripts for automatic deployment of Yoda Catalog.
- Ansible (>= 2.8)
- VirtualBox (>= 5.1)
- Vagrant (>= 1.9)
The catalog can be deployed on either CentOS 7 (>= 7.3), or on RHEL 8 / Alma Linux 8.
Configure the virtual machine for development:
vagrant upOn a Windows host first SSH into the Ansible controller virtual machine (skip this step on GNU/Linux or macOS):
vagrant ssh ilab-catalog-controller
cd ~/ilab-catalogDeploy Yoda Catalog to development virtual machine:
ansible-playbook playbook.ymlAdd following host to /etc/hosts (GNU/Linux or macOS) or %SystemRoot%\System32\drivers\etc\hosts (Windows):
192.168.70.10 ilab-catalog.ckan.test
Upgrading the Yoda Catalog development instance to the latest version can be done by running the Ansible playbooks again.
On a Windows host first SSH into the Ansible controller virtual machine (skip this step on GNU/Linux or macOS):
vagrant ssh controller
cd ~/ilab-catalogUpgrade Ansible scripts:
git pullUpgrade Yoda Catalog instance:
ansible-playbook playbook.ymlYoda Catalog uses CKAN as basis for catalog functionality.
CKAN is generic software that can be tailored.
It uses several modules / extensions to be able to form CKAN standard product into an application that can handle Yoda specific data.
A harvest source is a configuration, added within CKAN, to instruct where to harvest for data and how to deal with the harvested data from the source (in this case Yoda).
This by passing information to the ckan module CKANEXT-OAIPMH (see further)
Harvest sources, which is functionality added to CKAN by 3rd party module ‘ckan-harvester’, is mainly a configuration holding:
-endpoint
-params to tell configure the source freely as an application programmer
-harvest type (either CKAN/OAIPMH when OAI-PMH extension added)
CKANEXT HARVESTER uses a POSTGRESQL database to be able to harvest.
Harvesting is realised in following three stages:
-
Gather stage
Through OAI PMH gather all present datapackage and create a list of them in the postgresql database. -
Import stage
One by one handle the list of gather Ids and add them tot he database as a JSON-object separately. -
Fetch stage
The data that is fetched can now be processed and, in accordance with module CKANEXT-CUSTOM-THEME, be saved into CKAN itself. This has to be in alignment with the theme as the theme contains the ‘application’ and this needs to be ‘fed’ correctly from the database.
This goes especially for the extra – fields.
The processing of the fetched data is dealt with within another extension. CKANEXT-OAIPMH.
Thus, any party can tailor CKAN to its own wishes.
This extension is under development by the Yoda-team: CKANEXT-OAIPMH
A generic component that currently is used for catalog applications iLAB and EPOS.
It allows for harvesting through the OAI-PMH standard.
CKANEXT-OAIPMH processes the harvested data that was collected at the endpoint within the harvest source.
Driven by the parameters as stated in the CKAN harvest source that initiated the harvest process, CKANEXT-OAIPMH module can be configured to treat data differently corresponding to the active configuration. Thus, supporting the possibility for totally different applications.
In our case this component handles two entirey different sources for entirely different applications:
- EPOS, and
- ILAB
The differentiation can be made by passing the correct parameters into the Harvest source:
Configuration:
Voor ILAB datacite:
{"metadata_prefix": "datacite",
"application": "ILAB"
}
The CKAN-OAIPMH extension is programmed as such that it will provision CKAN based upon the above parameters. Main differentation is the application. Currently EPOS and iLAB.
metadataPrefix = datacite
The organisation linked to the harvest source is added to each datapackage as being the owning organisation (owner_org: see further CKAN fields).
Example ckan harvest source configuration:
{
"metadata_prefix": "datacite",
"application": "ILAB"
}
metadataPrefix = ISO
-Owner organisation is determined from within harvested data
NO new organisations are added programmatically when processing the harvested data.
Otto Lange, CKAN admin, controls this proces in the sense that he controls which organisations are known within CKAN.
If a passed organisation is present in CKAN already, that organisation is used as owner organisatin.
If not known within CKAN -> ‘Other lab’ is default.
Thus, organization ‘Other lab’ is an indicator of datapackages from unkown origins (from the point of view of CKAN).
-Maintainer is derived from harvest source organisation
Similarly like in iLAB the harvest source organisation is used.
For iLAB the harvest source organisation is used as owner organisation of a datapackage.
FOr EPOS however, the harvest source organisation is used maintainer of the datapackage.
Consequence of this is that maintainer organisations need to be added to CKAN as organisations. Otherwise, it is not possible to add the organisation to a harvest source. And consequently use it as maintainer regarding the harvested datapackage.
self.package_dict['maintainer'] = harvest_source.organisation
self.package_dict['maintainer_email'] = harvest_source.organisation.email
*-Specific EPOS 'package reference' handling *
Within the EPOS application there are 3 types of references regarding a package:
-supplement to
-cites
-references
Within the harvested XML that minimal information is passed regarding these references.
Therefore, lookup functionality is added to get more details via GFZ.
http://dataservices.gfz-potsdam.de/getcitationinfo.php?doi=http://dx.doi.org/' op basis van DOI
Based upon the received citation info, the CKAN package can be filled with more elaborate information.
This extra provisioning was deliberately created for EPOS handling - GFZ specifically. In order run this functionality, it must be added to the corresponding harvest source configuration.
example configuration for harvest source where extra information will be recovered for citations.
{
"metadata_prefix": "iso19139",
"application": "EPOS",
"collect_extra_info_from_gfz":"http://dataservices.gfz-potsdam.de/getcitationinfo.php?doi=http://dx.doi.org/",
"set":"~P3E9c3ViamVjdCUzQSUyMm11bHRpLXNjYWxlK2xhYm9yYXRvcmllcyUyMg"
}
when 'collect extra info' is left out, there will be not retrieval for this information and a simple list of doi's will be presented.
Email addresses for maintainers
Organisations (labs in CKAN) that will be used as maintainers, will have to have an email address as well.
Within CKAN this can only be done by adding extra fields. It is not a standard field on organization level.
Therefore use extra fields on organization level:
extras: [
{
value: "[email protected]",
state: "active",
key: "email",
revision_id: "b2356692-7f95-475e-88d3-1390451ccec7",
group_id: "7ad73491-aec5-4379-ae2c-44e03d05eaf4",
id: "2426a9b8-bfa3-4790-b5f9-f78d0d3eb2ee"
}
]
Standard CKAN fields
-author
Author of the package.
-owner_org
Organisation that owns the package and as such shown on the datapackage view
-title
Title of a package
-notes
Description of a package
-license_id
The license under which the datapackage can be used.
-url
URL referring to more detailed information regarding the datapackage
-groups
A datapackage can be linked to N groups.
-tags
A datapackage can be tagged to…
-formats
-maintainer
Reference to where the CKAN package is maintained.
-maintainer_email
-extras
Key value pairs enabling a CKAN programmer to customise datapackage data to
Extra fields for iLAB:
Locations covered
Dataset contact
Created at repository
Year of publicatoin
Publisher
Collection period
Mainly frontend items that transform standard CKAN into a tailored application. Eg. the iLAB catalog.
This by overruling view files, add static content like images and javascript.
This project is licensed under the GPL-v3 license. The full license can be found in LICENSE.