update dcatus v1.1 contactPoint writer to use position name for fn
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
## User Story
In order to transform more ISO records into valid dcatus 1.1, datagov wants to update the dcatus v1.1 contact point writer to allow position names to be used in lieu of a full name
## Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]
- [ ] GIVEN certain NOAA records prefer using position name over an individual or organization \
WHEN transformation happens \
THEN position name will be used as the `fn` when no individual or org is present \
[AND optionally another verifiable outcome]
## Background
user has notified us that "several branches" of NOAA prefer to use a position name instead of a individual or org element to avoid changing records during turnover.
## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))
[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
## Sketch
[Notes or a checklist reflecting our understanding of the selected approach]
Contributor guide
Assessment
This issue has not been assessed yet.