We now have both iso_entityType and adiwg_entityType. Do we want to rename iso_entityType? Otherwise, the mdEditor code will need to be adjusted to account for the prefix. It would be nice to have unique names without the prefix.

The data quality element type has been updated with the DQ_ prefix removed, this change needs to be reflected in the code list.

Suggest we change the codelist description to: "distributed computing platforms on which the operation has been implemented" or something like that. The current definition is unhelpful.

Shouldn't WwbService be WebServices?

Add namespace for spatialreference.org to "namespace" codelist (adiwg_namespace). This will allow greater flexibility for users to include custom coordinate reference systems by specifying a referenceSystemIdentifier from a source other than EPSG.

Proposal:
{
code: "spatialreference.org",
codeName: SR-ORG,
description: "Coordinate reference system from SpatialReference.org database"
}

Tests need to be updated to cover methods returning JSON.

Suggested additions:

• doi: digital object identifier URL
• orcid: Open Researcher and Contributor ID URL

Data quality requires a list of units. Add support for a basic list of units that can be used with data quality.

• Identifier namespace

Relative to ISO 19157-2013 Data Quality, add new codelist:

• Codelist Name: valueStructure
• Name: iso_valueStructure
• Source Name: DQM_ValueStructure
• Description:

Code: 001
Code Name: bag
Description: finite, unordered collection of related items (objects or values) that may be repeated (ISO 19107:2003)

Code: 002
Code Name: set
Description: unordered collection of related items (objects or values) with no repetition (ISO 19107:2003)

Code: 003
Code Name: sequence
Description: finite, ordered collection of related items (objects or values) that may be repeated (ISO 19107:2003)

Code: 004
Code Name: table
Description: an arrangement of data in which each item may be identified by means of arguments or keys (ISO/IEC 2382-4:1999)

Code: 005
Code Name: matrix
Description: rectangular array of numbers (ISO/
TS 19129:2009)

Code: 006
Code Name: coverage
Description: feature that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain (ISO 19123:2005)

The following items are needed to fully close out #52

• Verify and add missing parent classes
  • Add DQ_ThematicAccuracy
  • Add DQ_Metaquality
• Update codelist descriptions to match those in the XSD
  • Update description of DQ_PositionalAccuracy
  • Update description of DQ_TemporalQuality
  • Update description of DQ_LogicalConsistency
• Verify use of DQ_CoverageResult class

Missing parent classes

The adiwg_dataQualityElement.yml codelist contains several parent (abstract) classes such as DQ_PositionalAccuracy (AbstractDQ_PositionalAccuracy) and DQ_Completeness (AbstractDQ_Completeness), hovever, the following parent classes are not included in the list:

DQ_ThematicAccuracy (AbstractDQ_ThematicAccuracy). Add:

codeName: DQ_ThematicAccuracy
description: "accuracy of quantitative attributes and the correctness of non-quantitative attributes and of the classifications of features and their relationships"

see: https://standards.iso.org/iso/19157/-2/mdq/1.0/dataQualityElement.xsd

DQ_Metaquality (AbstractDQ_Metaquality). Add:

codeName: DQ_Metaquality
description: "accuracy of quantitative attributes and the correctness of non-quantitative attributes and of the classifications of features and their relationships"

See: https://standards.iso.org/iso/19157/-2/mdq/1.0/metaquality.xsd

Update codelist descriptions

The descriptions of several parent classes do not match those provided by the XSD (https://standards.iso.org/iso/19157/-2/mdq/1.0/dataQualityElement.xsd).

• AbstractDQ_PositionalAccuracy = "accuracy of the position of features"
• AbstractDQ_TemporalQuality = "accuracy of the temporal attributes and temporal relationships of features"
• AbstractDQ_LogicalConsistency = "degree of adherence to logical rules of data structure, attribution and relationships (data structure can be conceptual, logical or physical)"

Update the descriptions for DQ_PositionalAccuracy, DQ_TemporalQuality, and DQ_LogicalConsistency to match the descriptions for the above abstract classes.

Verify use of DQ_CoverageResult

DQ_CoverageResult doesn't seem to be a valid class. Should this be QE_CoverageResult? See:

• https://wiki.esipfed.org/QE_CoverageResult
• https://standards.iso.org/iso/19157/-2/mdq/1.0/dataQualityImagery.xsd

If so, change DQ_CoverageResult to:

codeName: QE_CoverageResult
description: "result of a data quality measure organising the measured values as a coverage"

iso_operationTypeCode.yml is actually listing the values for the MI_ObjectiveTypeCode not MI_OperationTypeCode.

Fields need to be updated to

• real
• simulated
• synthetic

After considering whether to use YAML or JSON for the codeList file I went with YAML because it has less syntax and most importantly the syntax of YAML is mostly local to the line. If we screw up a line of YAML it will likely only effect that line. While a missed comma or bracket in JSON could cripple the whole file (which actually could make it easier to catch errors to un-support my decision to go with YAML).

Below are two YAML format possibilities. The second one carries a definition for the codeList as well as the items, the first only supports the list items. Any preference?

# adiwgJson codelists
# compiled from ISO 19115-2, 19115-2, NGDC, and ADIwg

---
associationType:
  - {id: "001", codeName: crossReference, codeDesc: reference from one resource (dataset or project) to another}
  - {id: "002", codeName: largerWorkCitation, codeDesc: reference to a master resource (dataset or project) of which this one is a part}

characterSet:
  - {id: "001", codeName: ucs2, codeDesc: "16-bit fixed size Universal Character Set, based on ISO/IEC 10646"}
  - {id: "002", codeName: ucs4, codeDesc: "32-bit fixed size Universal Character Set, based on ISO/IEC 10646"}

classification:
  classDesc: name of the handling restrictions on the dataset
  items:
    - {id: "001", codeName: unclassified, codeDesc: available for general disclosure}
    - {id: "002", codeName: restricted, codeDesc: not for general disclosure}

Relative to ISO 19157-2013, add new codelist

• Codelist Name: evaluationMethodTypeCode
• Name: iso_evaluationMethodTypeCode
• Source Name: DQ_EvaluationMethodTypeCode
• Description: type of method for evaluating an identified data
  quality measure

Code: 001
Code Name: directInternal
Description: method of evaluating the quality of a data set based on inspection of items within the data set, where all data required is internal to the data set being evaluated

Code: 002
Code Name: directExternal
Description: method of evaluating the quality of a data set based on inspection of items within the data set, where reference data external to the data set being evaluated is required

Code: 003
Code Name: indirect
Description: method of evaluating the quality of a data set based on external knowledge

This will allow filtering of deprecated codelist entries.

Please review the TO and FROM conversion tables to ensure proper translation.

READER > from scienceBase to ADIwg

               @onlineFunction_sb2adiwg = [
                  {sb: 'arcgis', iso: nil},
                  {sb: 'browseImage', iso: 'browseGraphic'},
                  {sb: 'browsing', iso: 'browsing'},
                  {sb: 'citation', iso: nil},
                  {sb: 'configFile', iso: nil},
                  {sb: 'download',iso: 'download' },
                  {sb: 'emailService', iso: 'emailService'},
                  {sb: 'fileAccess', iso: 'fileAccess'},
                  {sb: 'kml', iso: nil},
                  {sb: 'mapapp', iso: nil},
                  {sb: 'method', iso: nil},
                  {sb: 'oai-pmh', iso: nil},
                  {sb: 'offlineAccess', iso: 'offlineAccess'},
                  {sb: 'order', iso: 'order'},
                  {sb: 'originalMetadata', iso: 'completeMetadata'},
                  {sb: 'pdf', iso: nil},
                  {sb: 'publicationReferenceSource', iso: nil},
                  {sb: 'repo', iso: nil},
                  {sb: 'search', iso: 'search'},
                  {sb: 'serviceCapabilitiesUrl', iso: nil},
                  {sb: 'serviceFeatureInfoUrl', iso: nil},
                  {sb: 'serviceLegendUrl', iso: nil},
                  {sb: 'serviceLink', iso: nil},
                  {sb: 'serviceMapUrl', iso: nil},
                  {sb: 'serviceWfsBackingUrl', iso: nil},
                  {sb: 'sitemap', iso: nil},
                  {sb: 'sourceCode', iso: nil},
                  {sb: 'txt', iso: nil},
                  {sb: 'upload', iso: 'upload'},
                  {sb: 'WAF', iso: nil},
                  {sb: 'webapp', iso: 'webApplication'},
                  {sb: 'webLink', iso: 'information'},
                  {sb: 'xls', iso: nil},
                  {sb: 'zip', iso: nil}
               ]

WRITER > from ADIwg to ScienceBase

               @onlineFunction_adiwg2sb = [
                  {iso: 'browseGraphic', sb: 'browseImage'},
                  {iso: 'browsing', sb: 'browsing'},
                  {iso: 'completeMetadata', sb: 'originalMetadata'},
                  {iso: 'dataUri', sb: nil},
                  {iso: 'doi', sb: nil},
                  {iso: 'download', sb: 'download'},
                  {iso: 'emailService', sb: 'emailService'},
                  {iso: 'fileAccess', sb: 'fileAccess'},
                  {iso: 'information', sb: 'webLink'},
                  {iso: 'offlineAccess', sb: 'offlineAccess'},
                  {iso: 'orcid', sb: nil},
                  {iso: 'order', sb: 'order'},
                  {iso: 'search', sb: 'search'},
                  {iso: 'upload', sb: 'upload'},
                  {iso: 'webApplication', sb: 'webapp'}
                ]

Not sure what happened, the formatting was fixed but then it reverted back to the wrong format, so it needs to be fixed again. This is related to the new code lists for data quality.

Please review the TO and FROM conversion tables to ensure proper translation.

READER > from scienceBase to ADIwg

               @role_sb2adiwg = [
                  {sb: 'administrator', iso: 'administrator'},
                  {sb: 'Associate Project Chief', iso: nil},
                  {sb: 'Author', iso: 'author'},
                  {sb: 'client', iso: 'client'},
                  {sb: 'Co-Investigator', iso: 'coPrincipalInvestigator'},
                  {sb: 'Contact', iso: 'pointOfContact'},
                  {sb: 'Cooperator/Partner', iso: 'collaborator'},
                  {sb: 'Custodian', iso: 'custodian'},
                  {sb: 'Data Owner', iso: 'owner'},
                  {sb: 'Data Provider', iso: nil},
                  {sb: 'Distributor', iso: 'distributor'},
                  {sb: 'Editor', iso: 'editor'},
                  {sb: 'funder', iso: 'funder'},
                  {sb: 'Funding Agency', iso: nil},
                  {sb: 'Lead Organization', iso: nil},
                  {sb: 'logistics', iso: 'logistics'},
                  {sb: 'Material Request Contact', iso: nil},
                  {sb: 'mediator', iso: 'mediator'},
                  {sb: 'Metadata Contact', iso: nil},
                  {sb: 'Originator', iso: 'originator'},
                  {sb: 'Participant', iso: nil},
                  {sb: 'Photographer', iso: nil},
                  {sb: 'Point of Contact', iso: 'pointOfContact'},
                  {sb: 'Principal Investigator', iso: 'principalInvestigator'},
                  {sb: 'Process Contact', iso: nil},
                  {sb: 'Processor', iso: 'processor'},
                  {sb: 'Project Chief', iso: nil},
                  {sb: 'Project Team', iso: nil},
                  {sb: 'publisher', iso: 'publisher'},
                  {sb: 'Referred By', iso: nil},
                  {sb: 'Report Prepared By', iso: nil},
                  {sb: 'Resource Provider', iso: 'resourceProvider'},
                  {sb: 'SoftwareEngineer', iso: nil},
                  {sb: 'sponsor', iso: 'sponsor'},
                  {sb: 'stakeholder', iso: 'stakeholder'},
                  {sb: 'Subtask Leader', iso: nil},
                  {sb: 'Supporter', iso: nil},
                  {sb: 'Task Leader', iso: nil},
                  {sb: 'Transmitted', iso: nil},
                  {sb: 'User', iso: 'use'},
                  {sb: 'USGS Mission Area', iso: nil},
                  {sb: 'USGS Program', iso: nil},
               ]

WRITER > from ADIwg to ScienceBase

               @role_adiwg2sb = [
                  {iso: 'administrator', sb: 'administrator'},
                  {iso: 'author', sb: 'Author'},
                  {iso: 'client', sb: 'client'},
                  {iso: 'coAuthor', sb: 'Author'},
                  {iso: 'collaborator', sb: 'Cooperator/Partner'},
                  {iso: 'contributor', sb: 'Cooperator/Partner'},
                  {iso: 'coPrincipalInvestigator', sb: 'Co-Investigator'},
                  {iso: 'custodian', sb: 'Custodian'},
                  {iso: 'distributor', sb: 'Distributor'},
                  {iso: 'editor', sb: 'Editor'},
                  {iso: 'funder', sb: 'funder'},
                  {iso: 'logistics', sb: 'logistics'},
                  {iso: 'mediator', sb: 'mediator'},
                  {iso: 'originator', sb: 'Originator'},
                  {iso: 'owner', sb: 'Data Owner'},
                  {iso: 'pointOfContact', sb: 'Point of Contact'},
                  {iso: 'principalInvestigator', sb: 'Principal Investigator'},
                  {iso: 'processor', sb: 'Processor'},
                  {iso: 'publisher', sb: 'publisher'},
                  {iso: 'resourceProvider', sb: 'Resource Provider'},
                  {iso: 'rightsHolder', sb: 'Data Owner'},
                  {iso: 'sponsor', sb: 'sponsor'},
                  {iso: 'stakeholder', sb: 'stakeholder'},
                  {iso: 'use', sb: 'User'}
               ]

Increment the minor version to 2.9.0

Should we use codes from http://www.iana.org/assignments/character-sets/character-sets.xhtml per 19115-1?

Should the dev branch be set as the default branch and have the master protected, following the same as mdEditor, mdKeywords, mdProfiles, and ideally all the others too?

Relative to implementing ISO 19157 Data Quality add an ADIwg codelist identifying Data Quality Element reports.

• Name: adiwg_qualityReportType
• Source: Alaska Data Integration working group
• Source Name: ADIwg_QualityReportType
• Description: the type of quality report

Code: 001
Code Name: completenessCommission
Description: excess data present in a data set

Code: 002
Code Name: completenessOmission
Description: data absent from a data set

Code: 003
Code Name: conceptualConsistency
Description: adherence to rules of the conceptual schema

Code: 004
Code Name: domainConsistency
Description: adherence of values to the value domains

Code: 005
Code Name: formatConsistency
Description: degree to which data are stored in accordance with the physical structure of
the data set

Code: 006
Code Name: topologicalConsistency
Description: correctness of the explicitly encoded topological characteristics of a data set

Code: 007
Code Name: absoluteExternalPositionalAccuracy
Description: closeness of reported coordinate values to values accepted as or
being true

Code: 008
Code Name: relativeInternalPositionalAccuracy
Description: closeness of the relative positions of features in a data set to their
respective relative positions accepted as or being true

Code: 009
Code Name: griddedDataPositionalAccuracy
Description: closeness of gridded data spatial position values to values accepted
as or being true

Code: 010
Code Name: thematicClassificationCorrectness
Description: comparison of the classes assigned to features or their attributes to a
universe of discourse (e.g. ground truth or reference data);

Code: 011
Code Name: thematicNonQuantativeAttributeCorrectness
Description: measure of whether a non-quantitative attribute is correct
or incorrect

Code: 012
Code Name: thematicQuantitativeAttributeAccuracy
Description: closeness of the value of a quantitative attribute to a value accepted
as or known to be true

Code: 013
Code Name: thematicAccuracyOfATimeMeasurement
Description: closeness of reported time measurements to values accepted as or
known to be true

Code: 014
Code Name: temporalConsistency
Description: correctness of the order of events

Code: 015
Code Name: temporalValidity
Description: validity of data with respect to time

Code: 016
Code Name: usabilityElement
Description: describes specific quality information about a data set’s suitability for a particular application or conformance to a set of requirements not defined in the standard quality reports

Code: 017
Code Name: metaqualityConfidence
Description: trustworthiness of a data quality result

Code: 018
Code Name: metaqualityRepresentativity
Description: degree to which the sample used has produced a result which is representative of the data within the data quality scope

Code: 019
Code Name: metaqualityHomogeneity
Description: expected or tested uniformity of the results obtained for a data quality evaluation

Add namespace for ORCID to "namespace" codelist (adiwg_namespace). This will be required to support the use of ORCID id's as external contact identifiers.

Proposal:
{
code: "orcid.org",
codeName: ORCID,
description: "ORCID Identifier"
}

Remove bower references from README.md

https://github.com/adiwg/mdCodes/blob/master/resources/iso_topicCategory.yml#L15

Bundle updates to make the gem compatible with ruby-head causes build failures in 1.9.3.

Any problems with this?

Add to namespace:

• org.adiwg.code.mapGridSystem
• org.adiwg.code.mapProjection

I have added the role of 'observer' to the iso_roleType codelist. This is to identify the role of taxonomic observer or person(s) making the species identification.

I added the role of 'curator' to the iso_roleType codelist. This is to identify the role of curator for specimens deposited in a repository to support taxonomic identification.

I think these roles were not inserted by ISO TC because taxonomy is an extension to the standards and not part of the ISO base. Let me know if there are objections or better terminology.

Relative to implementing ISO 19157 Data Quality add an ADIwg codelist identifying Evaluation Method report.

• Name: adiwg_evaluationMethod
• Source: Alaska Data Integration working group
• Source Name: ADIwg_EvaluationMethod
• Description: the type of Evaluation Method
• Note: evaluationMethod is the default method, while other methods are elemental variations to the default method

Code: 001
Code Name: evaluationMethod
Description: type of method used to evaluate quality of the data

Code: 002
Code Name: data
Description: data evaluation method

Code: 003
Code Name: fullInspection
Description: full inspection

Code: 004
Code Name: sampleBasedInspection
Description: sample based inspection

Code: 005
Code Name: aggregationDerivation
Description: aggregation or derivation method

Based on ISO 4217. See: https://en.wikipedia.org/wiki/ISO_4217#Active_codes

Based on list in https://www.geoplatform.gov/wp-content/uploads/2018/05/NGDA_Metadata_Guidelines_v3.pdf

---
-
    code: 001
    codeName: http://opengis.net/spec/wms
    Description: OGC Web Map Service (WMS)
-
    code: 002
    codeName: http://opengis.net/spec/wfs
    Description:  OGC Web Feature Service (WFS)
-
    code: 003
    codeName: http://opengis.net/spec/wcs
    Description:  OGC Web Coverage Service (WCS)
-
    code: 004
    codeName: http://opengis.net/spec/wmts
    Description:  OGC Web Map Tile Service (WMTS)
-
    code: 005
    codeName: http://opengis.net/spec/csw
    Description:  OGC Catalog Service (CSW)
-
    code: 006
    codeName: http://opengis.net/spec/kml
    Description:  OGC Keyhole Markup Language (KML)
-
    code: 007
    codeName: http://www.geoplatform.gov/spec/esri-map-rest
    Description:  Esri REST Map Service
-
    code: 008
    codeName: http://www.geoplatform.gov/spec/esri-image-rest
    Description:  Esri REST Image Service
-
    code: 009
    codeName: http://www.geoplatform.gov/spec/esri-feature-rest
    Description:  Esri REST Feature Service

The iso_dataQualityElement.yml is currently defined as:

• codelistName: "iso_dataQualityElement"
• source: "ISO"
• description: "ISO data quality elements"

The above implies that this is an approved ISO codelist. It is not. This is an ADIwg developed list of ISO "Data quality element" class names. To prevent any confusion with approved ISO codelists, the following changes should be made to the list properties:

• Rename the iso_dataQualityElement.yml and iso_dataQualityElement.json files to adiwg_dataQualityElement.*
• Update the codelist properties as follows:

codelistType: "staticList"
codelistName: "adiwg_dataQualityElement"
source: "Alaska Data Integration working group"
sourceName: "ADIwg_DataQualityElement"
extensible: true
description: "ISO data quality element class names"

Dependencies

The change may require updates to other toolkit components that use the codelist including:

• mdEditor
• mdTranslator
• mdTools

Update contribution guidelines to add business rules for creating new ISO code lists.

The following guidelines apply to ISO specified codelists (e.g. codelists.html, codelists.xml). The ISO "CI_DateTypeCode" codelist will be used for the following examples.

Specifying attributes for ISO maintained codelists

codelistName

1. Identify the desired ISO codelist name (e.g. "CI_DateTypeCode")
2. Remove class identifier prefix and "Code" suffix (CI_DateTypeCode -> DateType)
3. Convert shortened name to lowerCamelCase and add "iso_" prefix (DateType -> iso_dateType)
4. CI_DateTypeCode -> codelistName = iso_dateType
5. Use the newly created codelistName as the file name (e.g. iso_dateType.yml, iso_dateType.json)

source

1. Use value "ISO"

sourceName

1. Use the ISO specified codelist name. See the <cat:name> element from codelists.xml snippet below:

<cat:codelistItem>
<cat:CT_Codelist id="CI_DateTypeCode">
<cat:identifier>
<gco:ScopedName codeSpace="http://standards.iso.org/iso/19115/-3/cit/1.0">CI_DateTypeCode</gco:ScopedName>
</cat:identifier>
<cat:name>
<gco:ScopedName codeSpace="http://standards.iso.org/iso/19115/-3/cit/1.0">CI_DateTypeCode</gco:ScopedName>
</cat:name>

2. sourceName = "CI_DateTypeCode"

description

1. Use the ISO specified codelist description

<cat:definition>
<gco:CharacterString>identification of when a given event occurred</gco:CharacterString>
</cat:definition>

2. description = "identification of when a given event occurred"

code,codename,description

• gov.sciencebase.catalog,ScienceBase,ScienceBase is a cataloging and collaborative data management platform.
• urn:ISBN,ISBN,International Standard Book Number
• urn:ISSN,ISSN,International Standard Serial Number
• info:doi/,DOI,Digital Object Identifier
• info:ark/,ARK,Archival Resource Key
• urn:uuid, UUID, Universally unique identifier

The following items are needed to fully close out #37

• Identify perferrred list description
• Replace instances of "data set" with "dataset" (as per comment below, use "data set" spelling as in the standards document)

List description

The iso_evaluationMethodTypeCode.yml code list uses the description "type of method for evaluating an identified data quality measure", which seems to be based on https://standards.iso.org/iso/19157/resources/Codelists/gml/DQ_EvaluationMethodTypeCode.xml.

However, https://standards.iso.org/iso/19157/-2/mdq/1.0/codelists.xml and https://standards.iso.org/iso/19157/resources/Codelists/cat/codelists.xml both describe the list as "description of the evaluation method and procedure applied".

Which is the authoritative source for the DQ_EvaluationMethodTypeCode codelist?

Correct spelling of "data set"

The list item descriptions use the spelling "data set", this differs from ISO, which uses "dataset'.

This issue is a placeholder to review and discuss any outstanding issues related to the adiwg_evaluationMethod.yml codelist (see original isssue #40 and PR #53). It seems that this codelist is intended to represent the DQ_EvaluationMethod class names, however, in a more user friendly manner, intended to populate a mdEditor pick-list.

Items for review/discussion

• DQ_IndirectEvaluation is not in codelist
• DQ_EvaluationMethod is in the codelist, is that correct?

See:

• https://wiki.esipfed.org/DQ_EvaluationMethod
• https://standards.iso.org/iso/19157/-2/mdq/1.0/dataQualityEvaluation.xsd

DQ_IndirectEvaluation

The codelist does not include a DQ_IndirectEvaluation equivalent, however, it is described in the schema. See:

• https://wiki.esipfed.org/DQ_IndirectEvaluation
• https://standards.iso.org/iso/19157/-2/mdq/1.0/dataQualityEvaluation.xsd
• adiwg/mdJson-schemas#226

DQ_EvaluationMethod

The DQ_EvaluationMethod seems to be an abstract parent class that must be one of:

• mdq:DQ_AggregationDerivation
• mdq:DQ_FullInspection
• mdq:DQ_SampleBasedInspection
• mdq:DQ_IndirectEvaluation

Can DQ_EvaluationMethod stand on it's own without specifying any of the above? If not, should it be in the codelist?

Correlating the ISO and sbJSON association types get murky when reading the provided definitions. In particular not to let the code name influence the direction of the reference. From reading the documentation I assume the direction to be 'how the associated resource relates to the main resource'. So, 'the associated resource IS A __________ of the main resource.'

crossReference

• ISO: reference from one resource (dataset or project) to another
• Restated: the associated resource is reference to another dataset or project
  Note: non-specific, non-directional

largerWorkCitation

• ISO: reference to a master resource (dataset or project) of which this one is a part
• Restated: the associated resource is a citation of master resource to the main resource

partOfSeamlessDatabase

• ISO: part of the same structured set of data held in a computer
• Restated: the associated resource is a part of the same structured set of data as the main resource

source

• ISO: mapping and charting information from which the dataset content originates
• Restated: the associated resource is mapping and charting information from which the main resource content originates

steroMate

• ISO: part of a set of imagery that when used together, provides three-dimensional images
• Restated: the associated resource is part of a set of imagery that when used together provide three-dimensional images
  Note: no specific relationship to the main resource.

isComposedOf

• ISO: reference to resources (datasets or projects) that are parts of this resource
• Restated: the associated resource is a dataset or project that is part of the main resource

collectiveTitle

• ISO: common title for a collection of resources. NOTE Title identifies elements of a series collectively, combined with information about what volumes are available at the source cite.
• Restated: the associated resource is a common title for a collection of resources
  Note: no specific relationship to the main resource,

series

• ISO: associated through a common heritage such as produced to a common product specification
• Restated: the associated resource was produced via the same product specification as the main resource

dependency

• ISO: associated through a dependency
• Restated: the associated resource is dependent on the main resource
  Note: direction of dependency is uncertain

revisionOf

• ISO: resource is a revision of associated resource
• Restated: the main resource is revision of the associated resource
  Note: reverses direction

projectProduct

Note: deprecated by productOf. However, productOf is this relationship but in the reverse direction.

• Recommendation: Reinstate. Rename to 'product'.

supplementalResource

• ADIwg: supplemental resource
• Restated: the associated resource is a supplemental resource to the main resource

produced

• ADIwg: reference to a product or deliverable produced by the resource (e.g. project or program)
• Restated: the associated resource is product produced from the main resource
  Note: Verb?

• Recommendation: Drop this one. Repetitive and the verb is confusing.

productOf

• ADIwg: reference to a project or program which produced the resource as a deliverable
• Restated: the associated resource is the project or program which produced the main resource
  Note: The code and definition reverse the relationship direction from associated resource -> main resource to how the main resource relates to the associated resource.

• Recommendation: Drop this one. Same as 'largerWorkCitation' and the renamed 'parentProject'.

mainProjectOf

• ADIwg: reference to a project which is a derivative of the resource
• Restated: the associated resource is sub-project of the main resource
  Note: The code and definition reverse the relationship direction from associated resource -> main resource to how the main resource relates to the associated resource.

• Recommendation: Rename to 'subProject'

subProjectOf

• ADIwg: reference to a project of which the resource is a derivative
• Restated: the associated resource is a parent project of the main resource
  Note: The code and definition reverse the relationship direction from associated resource -> main resource to how the main resource relates to the associated resource. Same as 'largerWorkCitation'.

• Recommendation: Rename to 'parentProject'

• Recommendation: Replace the mdCodes definitions with the restated definitions above.

resources/iso_geometryTypeCode.yml

Code name should be strip, not stripe

https://standards.iso.org/iso/19115/resources/Codelists/gml/MI_GeometryTypeCode.xml

https://wiki.esipfed.org/ISO_19115-3_Codelists#MI_GeometryTypeCode

Discovered this when importing to Data.gov, caused validation to fail.

NonQuantitativeAttributeAccuracy is missing from the adiwg_dataQualityElement code list.

Related to adiwg/mdJson-schemas#285

Rename dev branch for consistency across mdToolkit

• Change default branch from dev to develop
• Add branch protections to develop branch

Please review the TO and FROM conversion tables to ensure proper translation.

READER > from scienceBase to ADIwg

               @scope_sb2adiwg = [
                  {sb: 'Collection', iso: 'collection'},
                  {sb: 'Data', iso: 'dataset'},
                  {sb: 'Data Release - In Progress', iso: nil},
                  {sb: 'Image', iso: 'photographicImage'},
                  {sb: 'map', iso: 'map'},
                  {sb: 'Physical Item', iso: 'sample'},
                  {sb: 'Project', iso: 'project'},
                  {sb: 'Publication', iso: 'publication'},
                  {sb: 'Software', iso: 'software'},
                  {sb: 'Web Site', iso: 'website'}
               ]

WRITER > from ADIwg to ScienceBase

               @scope_adiwg2sb = [
                  {iso: 'aggregate', sb: nil},
                  {iso: 'application', sb: 'Application'},
                  {iso: 'attribute', sb: nil},
                  {iso: 'attributeType', sb: nil},
                  {iso: 'awardInfo', sb: nil},
                  {iso: 'collection', sb: 'Collection'},
                  {iso: 'collectionHardware', sb: nil},
                  {iso: 'collectionSession', sb: nil},
                  {iso: 'collectionSite', sb: nil},
                  {iso: 'coverage', sb: nil},
                  {iso: 'dataDictionary', sb: nil},
                  {iso: 'dataset', sb: 'Data'},
                  {iso: 'dimensionGroup', sb: nil},
                  {iso: 'document', sb: 'Document'},
                  {iso: 'drawing', sb: nil},
                  {iso: 'factSheet', sb: nil},
                  {iso: 'feature', sb: nil},
                  {iso: 'featureType', sb: nil},
                  {iso: 'fieldSession', sb: nil},
                  {iso: 'initiative', sb: nil},
                  {iso: 'map', sb: 'map'},
                  {iso: 'metadata', sb: nil},
                  {iso: 'model', sb: nil},
                  {iso: 'nonGeographicDataset', sb: nil},
                  {iso: 'photographicImage', sb: 'Image'},
                  {iso: 'presentation', sb: nil},
                  {iso: 'product', sb: nil},
                  {iso: 'project', sb: 'Project'},
                  {iso: 'propertyType', sb: nil},
                  {iso: 'publication', sb: 'Publication'},
                  {iso: 'report', sb: 'Report'},
                  {iso: 'repository', sb: nil},
                  {iso: 'sample', sb: 'Physical Item'},
                  {iso: 'sciencePaper', sb: 'Report'},
                  {iso: 'series', sb: nil},
                  {iso: 'service', sb: nil},
                  {iso: 'software', sb: 'Software'},
                  {iso: 'tabularDataset', sb: 'Data'},
                  {iso: 'tile', sb: nil},
                  {iso: 'userGuide', sb: nil},
                  {iso: 'website', sb: 'Web Site'}
               ]

This is the code list
(removed)

There is a needed change to the Md_Scope codelist as indicated in isotc211: https://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ScopeCode
and confirmed by ISO 19115-1, 2014 amendment as follows:

Drop "geographic" from definition:

• dataset: information applies to a geographic dataset
• dataset: information applies to a dataset

Please review the TO and FROM conversion tables to ensure proper translation.

READER > from scienceBase to ADIwg

               @date_sb2adiwg = [
                  {sb: 'Acquisition', iso: 'acquisition'},
                  {sb: 'adopted', iso: 'adopted'},
                  {sb: 'AssessmentDate', iso: 'assessment'},
                  {sb: 'Award', iso: 'award'},
                  {sb: 'beginPosition', iso: nil},
                  {sb: 'Collected', iso: 'collected'},
                  {sb: 'creation', iso: 'creation'},
                  {sb: 'deprecated', iso: 'deprecated'},
                  {sb: 'distribution', iso: 'distribution'},
                  {sb: 'Due', iso: 'due'},
                  {sb: 'End', iso: 'end'},
                  {sb: 'endPosition', iso: nil},
                  {sb: 'firstProcessed', iso: nil},
                  {sb: 'info', iso: nil},
                  {sb: 'inForce', iso: 'inForce'},
                  {sb: 'lastProcessed', iso: nil},
                  {sb: 'lastRevision', iso: 'lastRevision'},
                  {sb: 'lastUpdate', iso: 'lastUpdate'},
                  {sb: 'nextUpdate', iso: 'nextUpdate'},
                  {sb: 'Publication', iso: 'publication'},
                  {sb: 'Received', iso: 'received'},
                  {sb: 'Release', iso: 'released'},
                  {sb: 'Reported', iso: 'reported'},
                  {sb: 'Repository Created', iso: nil},
                  {sb: 'Repository Updated', iso: nil},
                  {sb: 'revision', iso: 'revision'},
                  {sb: 'Start', iso: 'start'},
                  {sb: 'suspended', iso: 'suspended'},
                  {sb: 'Transmitted', iso: 'transmitted'},
                  {sb: 'unavailable', iso: 'unavailable'},
                  {sb: 'validityBegins', iso: 'validityBegins'},
                  {sb: 'validityExpires', iso: 'validityExpires'}
               ]

WRITER > from ADIwg to ScienceBase

               @date_adiwg2sb = [
                  {iso: 'acquisition', sb: 'Acquisition'},
                  {iso: 'adopted', sb: 'Adopted'},
                  {iso: 'assessment', sb: 'AssessmentDate'},
                  {iso: 'award', sb: 'Award'},
                  {iso: 'collected', sb: 'Collected'},
                  {iso: 'creation', sb: 'creation'},
                  {iso: 'deprecated', sb: 'deprecated'},
                  {iso: 'distribution', sb: 'distribution'},
                  {iso: 'due', sb: 'Due'},
                  {iso: 'end', sb: 'End'},
                  {iso: 'expiry', sb: nil},
                  {iso: 'inForce', sb: 'inForce'},
                  {iso: 'lastRevision', sb: 'lastRevision'},
                  {iso: 'lastUpdate', sb: 'lastUpdate'},
                  {iso: 'nextUpdate', sb: 'nextUpdate'},
                  {iso: 'publication', sb: 'Publication'},
                  {iso: 'received', sb: 'Received'},
                  {iso: 'released', sb: 'Release'},
                  {iso: 'reported', sb: 'Reported'},
                  {iso: 'revision', sb: 'revision'},
                  {iso: 'start', sb: 'Start'},
                  {iso: 'suspended', sb: 'suspended'},
                  {iso: 'transmitted', sb: 'Transmitted'},
                  {iso: 'unavailable', sb: 'unavailable'},
                  {iso: 'validityBegins', sb: 'validityBegins'},
                  {iso: 'validityExpires', sb: 'validityExpires'}
               ]

• Merge develop -> master
• Tag & Release v2.9.3

productOf, produced: https://www.sciencebase.gov/vocab/term/53d173c8e4b0536257c3415b
subprojectOf, mainprojectOf: https://www.sciencebase.gov/vocab/term/555a0f33e4b02fbcc17a9f3c

Please review the TO and FROM conversion tables to ensure proper translation.

READER > from scienceBase to ADIwg

               @progress_sb2adiwg = [
                  {sb: 'Active', iso: 'onGoing'},
                  {sb: 'Approved', iso: 'accepted'},
                  {sb: 'Completed', iso: 'completed'},
                  {sb: 'In Progress', iso: 'onGoing'},
                  {sb: 'Proposed', iso: 'proposed'}
               ]

WRITER > from ADIwg to ScienceBase

               @progress_adiwg2sb = [
                  {iso: 'accepted', sb: 'Approved'},
                  {iso: 'cancelled', sb: nil},
                  {iso: 'completed', sb: 'Completed'},
                  {iso: 'deprecated', sb: nil},
                  {iso: 'final', sb: nil},
                  {iso: 'funded', sb: nil},
                  {iso: 'historicalArchive', sb: nil},
                  {iso: 'notAccepted', sb: nil},
                  {iso: 'obsolete', sb: nil},
                  {iso: 'onGoing', sb: 'In Progress'},
                  {iso: 'pending', sb: nil},
                  {iso: 'planned', sb: nil},
                  {iso: 'proposed', sb: 'Proposed'},
                  {iso: 'required', sb: nil},
                  {iso: 'retired', sb: nil},
                  {iso: 'superseded', sb: nil},
                  {iso: 'suspended', sb: nil},
                  {iso: 'tentative', sb: nil},
                  {iso: 'underDevelopment', sb: nil},
                  {iso: 'valid', sb: nil},
                  {iso: 'withdrawn', sb: nil}
               ]

Please review the TO and FROM conversion tables to ensure proper translation.

Note mdCodes associationType is changed from what is currently shown on mdTools. The current codelist is shown in the WRITER section below. The following codes were added or modified to support the following associations:

• a project resource identifies a product
• a project resource identifies a subProject
• a project resource identifies a parentProject
• a data resource identifies a parentProject
• a data resource identifies a derivativeProduct

The following codes were deprecated

• mainprojectOf
• produced
• productOf
• projectProduct
• subProjectOf

READER > from scienceBase to ADIwg

               @association_sb2adiwg = [
                  {sb: 'alternate', iso: 'crossReference', reverse: 'alternate'},
                  {sb: 'constituentOf', iso: 'isComposedOf', reverse: 'constituent'},
                  {sb: 'copiedFrom', iso: nil, reverse: 'copiedInto'},
                  {sb: 'derivativeOf', iso: 'derivativeProduct', reverse: 'derived'},
                  {sb: 'precededBy', iso: nil, reverse: 'succeededBy'},
                  {sb: 'productOf', iso: 'parentProject', reverse: 'produced'},
                  {sb: 'related', iso: nil, reverse: 'related'},
                  {sb: 'subprojectOf', iso: 'subProject', reverse: 'mainprojectOf'}
               ]

WRITER > from ADIwg to ScienceBase

               @association_adiwg2sb = [
                  {iso: 'collectiveTitle', sb: nil},
                  {iso: 'crossReference', sb: 'alternate'},
                  {iso: 'dependency', sb: nil},
                  {iso: 'derivativeProduct', sb: 'derivativeOf'},
                  {iso: 'isComposedOf', sb: 'constituentOf'},
                  {iso: 'largerWorkCitation', sb: nil},
                  {iso: 'parentProject', sb: 'productOf'},
                  {iso: 'partOfSeamlessDatabase', sb: nil},
                  {iso: 'product', sb: 'productOf'},
                  {iso: 'revisionOf', sb: nil},
                  {iso: 'series', sb: nil},
                  {iso: 'source', sb: nil},
                  {iso: 'stereoMate', sb: nil},
                  {iso: 'subProject', sb: 'subprojectOf'},
                  {iso: 'supplementalResource', sb: nil},

                  {iso: 'mainprojectOf', sb: 'subprojectOf', deprecated: true},
                  {iso: 'produced', sb: 'productOf', deprecated: true},
                  {iso: 'productOf', sb: 'productOf', deprecated: true},
                  {iso: 'projectProduct', sb: 'productOf', deprecated: true},
                  {iso: 'subprojectOf', sb: 'subprojectOf', deprecated: true}
               ]