QA/QC Fixes
Last updated
Was this helpful?
Last updated
Was this helpful?
(1) Products need to have a specific resource type selected (not âproductâ) AND they need to be valid resource types. See .
(2) Responsible Parties need to have a valid role selected. See .
(3a) Ensure you have a single version of your data.gov tag and it is consistent across all of your items. See .
(3b) If you update your Metadata Repositories in mdJSON and publish to ScienceBase, you will also need to delete the erroneous version from ScienceBase (called Harvest Sets in SB). The issue is that SB doesnât remove tags when an item is republished, it just adds to tags. This issue applies to all keywords, but it is most important to fix for Harvest Sets. This scenario can happen with both erroneous data.gov tags or misspelled Harvest Set tagging.
You may want to consider using the injector script to delete or replace erroneous versions from mdJSON. You would still be required required to manually remove the erroneous versions from SB items.
(4) LCC allocations need to list the funding agency as the source (e.g., U.S. Fish and Wildlife Service), not the LCC. See .
Additionally, all funding from other FWS programs need to list FWS as the source (and not list the source as Fisheries, specific Refuges, ES, etc.). Clarifications on the exact program or refuge where the funding came from can be done through the Funding/Other Contacts field (and choose the role of "administrator").
(5) All allocations should list the fiscal year when the funds were allocated (this is different than a project's overall start and end dates - those are entered in Main/Time Period). There should be only a single fiscal year identified per allocation. Use the âPick a Fiscal Yearâ dropdown to autofill the date fields.
(6) All allocation recipients should be an Organization, not an Individual contact. Clarifications, although not required, can be done through the Funding/Other Contacts field (e.g., list a "principalInvestigator").
Note: this is a static list that was generated during the initial creation of the Science Catalog. The spreadsheet will not update when you fix an issue listed. Please update the "Fixed" column to "yes" when you have addressed a particular item.
Note: Matt Heller is looking into a solution (mid-November) using the injector script so data managers could run this automated process themselves to meet minimum requirements.
(15) Template scripting introduced some errors for some LCCs. Fixing these may be most effective with the injector script. Specific details related to these issues will be discussed with those who used the template scripting.
(7) All contacts need the appropriate contactType identifiedâthis is particularly important for funding summaries. See .
(8) Address the .
(9) Fix âconsevation designâ Typo. Select correct option in mdEditor and re-publish. Affected records can be viewed (this is a link to a saved Science Catalog search for the erroneous keyword).
(10) Distribution links need to be included for products. This was already required for all products and this is particularly critical for items sent to data.gov. This is the only online resource data.gov reads so without a URL here, there is no way for a user to access the actual product. The recommended role is "distributor" (see the section for more info).
(11) Republish any records that donât have mdJSON attached (without mdJSON, the item will not show up in the Science Catalog). See .
(12) Go through errors/warnings in the (e.g., no ISO Keyword, bad repo tag, etc.) .
(13) Address remaining .
(14) Fix the errors identified by the ASG in manual QA/QC checks of the Science Catalog. .