DCAT-us writer: accessLevel

[hmaier-fws]

Issue

Determine mapping to use when writing the DCAT-US accessLevel field. The field is defined as:

Description:
The degree to which this dataset could be made publicly-available, regardless of whether it has been made available. Choices: public (Data asset is or could be made publicly available to all without restrictions), restricted public (Data asset is available under certain use restrictions), or non-public (Data asset is not available to members of the public).

Accepted values:
Must be one of the following: “public”, “restricted public”, “non-public”

Usage Notes:
This field refers to the degree to which this dataset could be made available to the public, regardless of whether it is currently available to the public. For example, if a member of the public can walk into your agency and obtain a dataset, that entry is public even if there are no files online. A restricted public dataset is one only available under certain conditions or to certain audiences (such as researchers who sign a waiver). A non-public dataset is one that could never be made available to the public for privacy, security, or other reasons as determined by your agency.

Potential mappings:

1) Extend MD_RestrictionCode codelist

Codelist could be extended to include: "public", "restricted public", and "non-public"

2) Remap existing codes

Since the three DCAT-US access levels are extremely general, it may be possible to crosswalk the existing MD_RestrictionCode and MD_ClassifoicationCode values to the values in the DCAT-US list.

mdJSON source:

• resourceInfo.constraint.legal.accessConstraint
• resourceInfo.constraint.security.classification

Related issues: #251, #264

[hmaier-fws]

We need to create user documentation that describes how the various ISO codes (MD_ClassificationCode, etc.) could map to the DCAT-US values above.