Write code to generate a DCAT file from EML

[peterdesmet]

Once we have the mapping described (see #1), we can implement it so that when a dataset is (re)published on the IPT, a DCAT file of the metadata is created in addition to the EML metadata. There are two different approaches:

As part of the IPT code base

Advantages:

• We can make use of the EML Java classes exposed by the IPT (https://github.com/gbif/gbif-metadata-profile)
• We can potentially make use of the same plugin as gbif-doi to express DCAT as GBIF classes (see resources)
• We can tap in the publication code to create a DCAT metadata file each time a dataset is (re)published
• The functionality becomes part of the IPT (open source) code base and could in collaboration with GBIF be rolled out for all IPTs

Disadvantages:

• We're restricted to Java to write the functionality

As a separate script

Advantages:

• More choice of software language
• No constraints imposed by IPT code

Disadvantages

• None of the advantages of making it part of the IPT code
• The script has to rely on the published EML file instead of the EML standard expressed as classes
• The script has to be triggered in some way separately from the IPT (e.g. a cron job)

[peterdesmet]

We decided to implement this in the IPT code.