boilerplate for DwC-A EML

[mobb]

the EML for Darwin Core archives (a L2) will come from the L1 (ecocomDP) dataset, or boilerplate.

Boilerplate we need:

• [x] paragraph for abstract
• [x] phrase to add to title
• [x] IR (edi default)
• [x] keywordSet for DC terms

[clnsmth]

Phrase to add to title will be "(Reformatted to a Darwin Core Archive)". E.g. Ant Assemblages in Hemlock Removal Experiment at Harvard Forest since 2003 (Reformatted to a Darwin Core Archive)

[clnsmth]

@mobb I presume "IR" means Intellectual Rights. Why would this not be the L0 IR? Our current practice is to use the L0 IR but replace it with the EDI default if missing.

[clnsmth]

@mobb How about this for the abstract?

"This data package is formatted as a Darwin Core Archive (DwC-A, occurrence (or event) core). For more information on Darwin Core see https://www.tdwg.org/standards/dwc/. This Level 2 data package was derived from the Level 1 data package found here: PARENT_PACKAGE_URL, which was derived from the Level 0 data package found here: L0_PACKAGE_URL. The abstract below was extracted from the Level 0 data package and is included for context: ... "

[clnsmth]

@mobb We should probably add a note about how these data were converted from an ecocomDP to the DwC-A in the EML methods, as we do for ecocomDP data packages. Proposed text:

"This data package is a child (Level 2) of the parent data package (Level 1) listed in the dataSource element below. This Level 2 data package was created using the L1_to_L2_DwCA() function of the ecocomDP R library. Methods of the Level 0 (original source dataset) are included for context: ..."

[clnsmth]

@mobb Should we have a unique keyword to tag DwC-A derived from ecocomDP packages? This could help with maintenance and other tasks. If so, what should it be?

[mobb]

@clnsmth Re IR - EDI default will be fine. since we are using EAL, its built in, so nothing more to do.

Re abstract: both those statements are great! go for it.

[mobb]

@mobb Should we have a unique keyword to tag DwC-A derived from ecocomDP packages? This could help with maintenance and other tasks. If so, what should it be?

Been thinking about that. I think including the term "ecocomDP" in a keyword for L2 will be confusing, since it will also be pulled up with the L1. maybe just "Darwin Core Archive (DwC-A) Event Core"?

Ideally, a reprocess will be triggered by an event notification. we'll have to see how that goes!

[clnsmth]

@clnsmth Re IR - EDI default will be fine. since we are using EAL, its built in, so nothing more to do.

Re abstract: both those statements are great! go for it.

ecocomDP::make_eml_dwca() will be a wrapper to EMLassemblyline::make_eml() enabling us to merge the parent and child metadata. So we can leave the IR "as is" or change it. Why not preserve the L0 IR, as we are currently doing for the L1?

[clnsmth]

@mobb Is there standard set of keywords to accompany each DwC-A event core and occurrence core, or will they vary with dataset content?

[clnsmth]

Keywords for occurrence core and event core are stashed in /inst/dwca_occurrence_core and /inst/dwca_event_core, respectively.