Add permit_id as a core model property

[datadavev]

One or more permits are often associated with collection of physical samples, and there is a need to ensure that information is available with the sample records.

Task here is to add support for a multi-valued field to store permit ids with sample records. This should be a string field (i.e. not tokenized) with the assumption of storing some sort of identifier. In practice, it is likely values in this field will at least by quite variable since there's no formal representation of how this information is associated with records.

Initial use case is in support of GEOME and the FAIR Island project. Permit info will be added to the GEOME field permitInformation, an optional field that is attached to GEOME Event records. Some examples of entries in this field include:

1187/SU/KS/2006, 04239/ SU.3/KS/2019
LIPI 1187/SU/KS/2006 and 04239/SU.3/KS/2006
Commonwealth of Australia Torres Strait Fisheries Act 1984 Permit for Scientific purposes; Australian Fisheries Management Authority, Thursday Island
DAFF/DEA
NA
"Permit to EC and JD from Ministry of Fisheries and Forests, Export permit Permit C300/3019"
AU-COM2008042; Australian Government

We need to:

• Add a multi-valued string field to solr
• populate the field from GEOME records (should an attempt be made to parse what looks like multiple IDs?)
• Expose the field in isamples core records
• Support display of this field in the UI
• Support search against this field

[datadavev]

Example spreadsheet with permit info provided by John in GDrive at: https://drive.google.com/drive/u/0/folders/1cIPzlGILRqG3Ip9477bsfJclCDpY1rVR

[datadavev]

After further discussion with Neil, it seems there's a need for two properties: complies_with, and authorized_by.

[datadavev]

Initial content will be added to GEOME records in the permitInformation field with the recommendation to use a structured format like:

permitInformation="complies_with:COMPLIES1;COMPLIES2 authorized_by:AUTHORIZED1;AUTHORIZED2"

Where:

• COMPLIESn is a pointer to the associated compliance documentation, ideally in the form of one or more URIs.
• AUTHORIZEDn is a pointer to the associated permit(s) authorizing the activity, ideally in the form of one or more URIs.

[smrgeoinfo]

looks like the permitInformation is concatenated in the description field. Is it important enough to add in a separate field on SamplingEvent or on Site?

[datadavev]

This was an early suggestion as there was a single field in GEOME for capturing permitInformation. GEOME is being updated to provide different fields for cultural and legal references, and I believe each will be multi-valued.

Having multiple fields for this info makes it much simpler for everyone.

[smrgeoinfo]

see issue in metadata repo metadata/#102

[dannymandel]

It sounds like this one should stay open as we are anticipating further changes on the GEOME side to adopt it.