Add terms definitions into H2.0 UI

[tdlowden]

User Story

As a harvest source POC, I want a way to view the definitions or correlated meanings of terms, so that I can better understand my harvest source information

• Frequency
• Source_type
• Schema_type
• Records with CKAN_id
• Email
• Records_ignored
• Job errors vs record errors
• Cited job/harvest/org IDs
• record errors messages

Acceptance Criteria

• GIVEN a harvest source POC visits the H2.0 UI
  WHEN job or harvest pages are visited
  THEN key terms listed above should have a link or glossary or hover effect to define them

Background

https://docs.google.com/document/d/1ktdicfssXhtjyYnkdvi1q7GCEDDMWAfv1kDrvnxUcL8/edit?tab=t.0

Security Considerations (required)

None

Sketch

• Decide most appropriate way to surface key term definitions (hover, glossary, etc)
• Implement chosen method in H2.0 UI

[rshewitt]

• Frequency
  • how often the harvest source is harvested ( i.e. extracted, transformed, and loaded into our catalog ). examples are "weekly", "daily", and "manual"
• Source_type
  • either a single document ( e.g. data.json ) or a web-accessible folder with many documents
• Schema_type
  • the metadata standard of the document(s). examples include ISO19115-1, ISO19115-2, CSDGM, and DCAT-US. only 1 schema can be used per harvest source.
• Records with CKAN_id
  • we use a combination of open source and in-house software in our harvesting. currently, our records are synchronized between these 2 systems by pairing the id of the record in our in-house database with our open source (i.e. CKAN) database.
• Email
  • an email address to receive harvesting information
• Records_ignored
  • our harvesting process pulls data from our internal database and your external source and compares them to determine which records need to be created, updated, deleted, or ignored on our end. "ignored" means nothing needs to be done. we have the most recent copy of your record. in comparison to "created", let's say, where we don't have a copy of your record and need to create it on our end.
• Job Errors
  • also known as "critical" errors are ones which prevent the harvester from determining which operations to run on records. for example, if the harvester receives a 404 http error code when attempting to download your document this would produce a "Job Error".
• Record Error
  • also known as "non-critical" errors are ones which occur at the record level after the harvester has determined which operations to run. examples include validation and transformation failure.

Cited job/harvest/org IDs
record errors messages