Smithsonian / Smithsonian/caas-aspace-scripts
[INVESTIGATE] Research Regular Data Quality Checks for ASpace Metadata
@crugas is already working on this.
Since Apr 21, 2025.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Research what kinds of metadata are useful for running regularly occurring data quality checks against. Some of the kinds of data we are considering include:
- Invalid dates (begin date after end, non-ISO formatted)
- Items listed as collections for their description level
- Top containers without indicators?
- Resources without EAD IDs?
- Duplicate subjects
- Duplicate agents
- Resources without Creator agents?
- Top containers not linked to resources/archival objects
Describe the solution you'd like
A behavior-driven-development model of requirements for what kinds of data we want to check and how to check for them.
Describe alternatives you've considered
Investigating different methods of running, capturing, and reporting on these data quality checks. We already have a process in place where reports on metadata quality are put in the BestPracticeReports in the SOVA dropbox. It would be good to get a list of all the checks that are run for these reports.
Additional context
Related: Harmonize URI entries (full URI vs. ID) in ASpace subjects and agents - this is an example of a report we could run regularly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.