diff --git a/_quarto.yml b/_quarto.yml index 27503cf..001432b 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -130,7 +130,6 @@ website: - section: "Appendix" href: content/appendix/appendix_overview.qmd contents: - - content/appendix/non_duplication_policy.qmd - section: "Developer Resources" href: content/developer_resources/developer_resources_overview.qmd contents: @@ -143,6 +142,7 @@ website: href: content/appendix/lcc_workflows/lcc_workflows_overview.qmd contents: - content/appendix/lcc_workflows/cofunded_lcc_projects.qmd + - content/appendix/non_duplication_policy.qmd # - content/archiving.qmd # - section: "Trouble-Shooting" diff --git a/_site/content/metadata_file_management/export.html b/_site/content/metadata_file_management/export.html index e40d052..2858c72 100644 --- a/_site/content/metadata_file_management/export.html +++ b/_site/content/metadata_file_management/export.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • diff --git a/_site/content/metadata_file_management/metadata_file_management_overview.html b/_site/content/metadata_file_management/metadata_file_management_overview.html index 8851ca0..eaf1556 100644 --- a/_site/content/metadata_file_management/metadata_file_management_overview.html +++ b/_site/content/metadata_file_management/metadata_file_management_overview.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • diff --git a/_site/content/metadata_requirements.html b/_site/content/metadata_requirements.html index 727d637..c7c0e2a 100644 --- a/_site/content/metadata_requirements.html +++ b/_site/content/metadata_requirements.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -661,6 +661,11 @@

    Projects and Product

    Main Tab

    +++++ @@ -676,13 +681,13 @@

    Main Tab

    - - + + - - + + @@ -706,18 +711,18 @@

    Main Tab

    - - + + - + - - + + @@ -761,8 +766,8 @@

    Main Tab

    - - + + @@ -771,21 +776,25 @@

    Main Tab

    - + - - + +
    Metadata Field
           TitleRequired*Required*RequiredRequired
           StatusRequired*Required*RequiredRequired
    Default Locale
           TitleRequired*Required*RequiredRequired
           Dates (multiple)Required*Required If Applicable
           Responsible Parties (multiple)Required*Required*RequiredRequired
           Online Resource
           AbstractRequired*Required*RequiredRequired
    Time Period
           Start DateRequired*Required If Applicable
           End DateRequired*Required*RequiredRequired
    -

    *Also required under the ScienceBase 30-day Policy

    Metadata Tab

    +++++ @@ -841,12 +850,16 @@

    Metadata Tab

    Metadata Field
    -

    *Also required under the ScienceBase 30-day Policy
    -

    +


    Keywords Tab

    +++++ @@ -912,6 +925,11 @@

    Extent Tab

    Taxonomy Tab

    Metadata Field
    +++++ @@ -937,6 +955,11 @@

    Taxonomy Tab

    Distribution Tab

    Metadata Field
    +++++ @@ -987,12 +1010,16 @@

    Distribution Tab

    Metadata Field
    -

    *Also required under the ScienceBase 30-day Policy
    -

    +


    Constraints Tab

    +++++ @@ -1038,6 +1065,11 @@

    Constraints Tab

    Funding Tab

    Metadata Field
    +++++ @@ -1053,22 +1085,22 @@

    Funding Tab

    - + - + - + - + @@ -1093,7 +1125,7 @@

    Funding Tab

    - + @@ -1103,7 +1135,7 @@

    Funding Tab

    Metadata Field
           AmountRequired*Required
           CurrencyRequired*Required
           Award IDRequired*Required
           SourceRequired*Required
           DatesRequired*Required
    -

    *Also required under the ScienceBase 30-day Policy

    +


    @@ -1112,6 +1144,11 @@

    Contacts

    Contacts Information

    +++++ diff --git a/_site/content/product_records/main_tab_product.html b/_site/content/product_records/main_tab_product.html index 40f3829..fc20ce9 100644 --- a/_site/content/product_records/main_tab_product.html +++ b/_site/content/product_records/main_tab_product.html @@ -69,6 +69,17 @@ "search-label": "Search" } } + + + @@ -102,7 +113,6 @@
    USFWS Science Applications Metadata Guidance
    -
    @@ -143,12 +153,6 @@ Projects, Products, Contacts - -
  • -
    - - Non-Duplication Policy -
  • @@ -518,24 +522,28 @@
    • +
  • +
    + + Feedback and Help +
    +
    • +
  • +
    + + Glossary +
    +
  • - - Trouble-Shooting + + Appendix
    -
    • -
  • +
  • Developer Resources @@ -543,7 +551,7 @@
    - -
    +

    Other Links

    @@ -675,11 +668,11 @@

    Main Tab

    • - + - + @@ -711,7 +704,7 @@

    Main Tab

    - + @@ -723,7 +716,7 @@

    Main Tab

    - + @@ -731,7 +724,7 @@

    Main Tab

    - + @@ -767,7 +760,7 @@

    Main Tab

    - + @@ -779,7 +772,7 @@

    Main Tab

    - +
    Metadata Field
           TitleRequired*Required
           StatusRequired*Required
    Default Locale
           Principal InvestigatorIf Applicable*If Applicable
           Co-Principal Investigator
           TitleRequired*Required
           Dates (multiple)
           Responsible Parties (multiple)Required*Required
           Online Resource
           AbstractRequired*Required
    Time Period
           End DateRequired*Required
    @@ -1298,7 +1291,7 @@

    Start Dat }); var localhostRegex = new RegExp(/^(?:http|https):\/\/localhost\:?[0-9]*\//); var mailtoRegex = new RegExp(/^mailto:/); - var filterRegex = new RegExp("https:\/\/studious-adventure-wo15nv1\.pages\.github\.io"); + var filterRegex = new RegExp("https:\/\/usfws\.github\.io\/Science_Applications_Metadata_Guidance\/"); var isInternal = (href) => { return filterRegex.test(href) || localhostRegex.test(href) || mailtoRegex.test(href); } diff --git a/_site/content/project_records/main_tab_project.html b/_site/content/project_records/main_tab_project.html index 13bb9de..442767c 100644 --- a/_site/content/project_records/main_tab_project.html +++ b/_site/content/project_records/main_tab_project.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -625,7 +625,7 @@

    On this page

  • Citation
    • -
    -

    Alternate Title (If desired)

    +
    +

    Alternate Title

    You can add an Alternate Title, if desired. Generally these should be shorter than the full Title.

    @@ -955,7 +955,7 @@

    Responsible P coPrincipalInvestigator Co-Investigators -Required, if applicable +If applicable diff --git a/_site/content/project_records/metadata_tab_project.html b/_site/content/project_records/metadata_tab_project.html index 08dcc37..480ec17 100644 --- a/_site/content/project_records/metadata_tab_project.html +++ b/_site/content/project_records/metadata_tab_project.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -626,7 +626,7 @@

    On this page

    -
  • Parent Metadata +
  • Parent Metadata (Required)
    • -
    -

    Parent Metadata

    +
    +

    Parent Metadata (Required)

    Parent Metadata tells mdEditor where the project metadata should go when it is published. If using ScienceBase, this is the folder above the project by default.

    If you imported the project metadata from ScienceBase originally, this section will be populated already.

    If you created the project metadata from scratch in mdEditor, this will be blank. If you provide a default parent ID in Settings (Publishing Settings for ScienceBase), this will be generated for you when when you publish. This is most likely your SA regional project folder. You can enter the parent item SBID directly in your individual metadata record if you wish.

    diff --git a/_site/content/project_records/project_records_overview.html b/_site/content/project_records/project_records_overview.html index 5f33f1e..c9007c1 100644 --- a/_site/content/project_records/project_records_overview.html +++ b/_site/content/project_records/project_records_overview.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • diff --git a/_site/content/roles_and_responsibilities.html b/_site/content/roles_and_responsibilities.html index d094172..55c74d1 100644 --- a/_site/content/roles_and_responsibilities.html +++ b/_site/content/roles_and_responsibilities.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -655,7 +655,7 @@

    ARDs

  • Responsible for supporting staff time and allocating resources to follow the SA Data Management Plan through their entire chain of command
  • Ensure data management responsibilities are followed when SA funds are allocated outside the Program (e.g., go to another FWS Program)
  • Ensure Performance Appraisal Plans reflect responsibilities for data stewardship
    • -
  • Sign memo stating a project intended for funding is not duplicative research or other science activity (Science Project) and therefore does not need to go through any additional steps in the Non-Duplication Policy.
    • +
  • Sign memo stating a project intended for funding is not duplicative research or other science activity (Science Project) and therefore does not need to go through any additional steps in the Non-Duplication Policy.
  • Sign ​CASC Consultation Certification memo​ stating the CASC consultation took place and identified not duplication of funding between SA and a CASC. For grants and cooperative agreements, this can be certified by checking the appropriate check box on the Award Checklist - FWS Form 3-2460.
    • diff --git a/_site/content/science_catalog.html b/_site/content/science_catalog.html index 0184a5b..759d145 100644 --- a/_site/content/science_catalog.html +++ b/_site/content/science_catalog.html @@ -69,6 +69,17 @@ "search-label": "Search" } } + + + @@ -102,7 +113,6 @@
    USFWS Science Applications Metadata Guidance
    -
    @@ -143,12 +153,6 @@ Projects, Products, Contacts - -
  • -
    - - Non-Duplication Policy -
  • @@ -518,24 +522,28 @@
    • +
  • +
    + + Feedback and Help +
    +
    • +
  • +
    + + Glossary +
    +
  • - - Trouble-Shooting + + Appendix
    -
    • -
  • +
  • Developer Resources @@ -543,7 +551,7 @@
    - -
    +

    Other Links

    @@ -687,7 +680,7 @@

    Fiscal Years Funded -Funding Tab: Allocation: Time Period: Dates +Funding Tab: Funding Period: Time Period: Dates Associated Project2 @@ -994,7 +987,7 @@

    Architecture

    }); var localhostRegex = new RegExp(/^(?:http|https):\/\/localhost\:?[0-9]*\//); var mailtoRegex = new RegExp(/^mailto:/); - var filterRegex = new RegExp("https:\/\/studious-adventure-wo15nv1\.pages\.github\.io"); + var filterRegex = new RegExp("https:\/\/usfws\.github\.io\/Science_Applications_Metadata_Guidance\/"); var isInternal = (href) => { return filterRegex.test(href) || localhostRegex.test(href) || mailtoRegex.test(href); } @@ -1339,4 +1332,4 @@

    Architecture

    - \ No newline at end of file + \ No newline at end of file diff --git a/_site/content/workflow/metadata_editing_republishing.html b/_site/content/workflow/metadata_editing_republishing.html index e34ddc5..4d5990a 100644 --- a/_site/content/workflow/metadata_editing_republishing.html +++ b/_site/content/workflow/metadata_editing_republishing.html @@ -543,12 +543,6 @@
    • +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -624,7 +624,6 @@

    On this page

  • 10. Publish your records
  • 11. Export your records
  • 12. Review Science Catalog
    • -
  • 13. Consult QA/QC resources.

    • Other Links

    @@ -702,10 +701,6 @@

    11. Export your record

    12. Review Science Catalog

    The SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.

    -
    -
    -

    13. Consult QA/QC resources.

    -

    See the QA/QC Fixes page for suggestions about updating your data to check your metadata.

    diff --git a/_site/content/workflow/metadata_from_scratch.html b/_site/content/workflow/metadata_from_scratch.html index f39c60d..72a71b4 100644 --- a/_site/content/workflow/metadata_from_scratch.html +++ b/_site/content/workflow/metadata_from_scratch.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -624,7 +624,6 @@

    On this page

  • 10. Publish your records
  • 11. Export your records
  • 12. Review Science Catalog
    • -
  • 13. Consult QA/QC resources.

    • Other Links

    @@ -708,10 +707,6 @@

    11. Export your record

    12. Review Science Catalog

    The SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.

    -
    -
    -

    13. Consult QA/QC resources.

    -

    See the QA/QC Fixes page for suggestions about updating your data to check your metadata.

    diff --git a/_site/content/workflow/metadata_sciencebase_first.html b/_site/content/workflow/metadata_sciencebase_first.html index 28318fe..b208c07 100644 --- a/_site/content/workflow/metadata_sciencebase_first.html +++ b/_site/content/workflow/metadata_sciencebase_first.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -624,7 +624,6 @@

    On this page

  • 10. Publish your records
  • 11. Export your records
  • 12. Review Science Catalog
    • -
  • 13. Consult QA/QC resources.

    • Other Links

    @@ -701,10 +700,6 @@

    11. Export your record

    12. Review Science Catalog

    The SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.

    -
    -
    -

    13. Consult QA/QC resources.

    -

    See the QA/QC Fixes page for suggestions about updating your data to check your metadata.

    diff --git a/_site/content/workflow/workflow_overview.html b/_site/content/workflow/workflow_overview.html index f5994e7..25ce36a 100644 --- a/_site/content/workflow/workflow_overview.html +++ b/_site/content/workflow/workflow_overview.html @@ -543,12 +543,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -626,7 +626,6 @@

    On this page

  • 10. Publish your records
  • 11. Export your records
  • 12. Review Science Catalog
    • -
  • 13. Consult QA/QC resources.

    • Other Links

    @@ -716,10 +715,6 @@

    11. Export your record

    12. Review Science Catalog

    The SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.

    -
    -
    -

    13. Consult QA/QC resources.

    -

    See the QA/QC Fixes page for suggestions about updating your data to check your metadata.

    diff --git a/_site/index.html b/_site/index.html index e012770..97bf4fd 100644 --- a/_site/index.html +++ b/_site/index.html @@ -542,12 +542,6 @@ +
  • +
    + + Non-Duplication Policy +
    +
    • @@ -667,12 +667,13 @@

    Who Should Use

    How to Use this Manual

    The recommended way to use this manual is directly accessing the pages from the internet. By doing so, you guarantee you are using the current version. This is a living document and will be updated as needed. The online version will also have the best functionality and graphical display.

    -

    This document will continue to be updated regularly and publishing using the GitHub Repository. Please refresh this manual every time you open it to ensure you are viewing the most recent version. Last updated: 15 October, 2024.

    +

    This document will continue to be updated regularly and publishing using the GitHub Repository. Please refresh this manual every time you open it to ensure you are viewing the most recent version.

    +

    Guidance was last updated: 15 October, 2024.

    Providing Feedback

    If you would like to provide feedback (e.g., comments, suggestions, etc.) about this guidance, you can use this online form.

    -

    If you’d like to give direct feedback through Github, please consider reporting an issue or submitting edits through a pull request. However, in order to access these functions, you will be required to sign in or create an account with Github.

    +

    If you’d like to give direct feedback through Github, please consider reporting an issue or submitting edits through a pull request. However, in order to access these functions, you will be required to sign in or create an account with Github.

    diff --git a/_site/search.json b/_site/search.json index 4751bcc..42fb0e1 100644 --- a/_site/search.json +++ b/_site/search.json @@ -44,7 +44,7 @@ "href": "index.html#how-to-use-this-manual", "title": "USFWS Science Applications Metadata Guidance", "section": "How to Use this Manual", - "text": "How to Use this Manual\nThe recommended way to use this manual is directly accessing the pages from the internet. By doing so, you guarantee you are using the current version. This is a living document and will be updated as needed. The online version will also have the best functionality and graphical display.\nThis document will continue to be updated regularly and publishing using the GitHub Repository. Please refresh this manual every time you open it to ensure you are viewing the most recent version. Last updated: 15 October, 2024.", + "text": "How to Use this Manual\nThe recommended way to use this manual is directly accessing the pages from the internet. By doing so, you guarantee you are using the current version. This is a living document and will be updated as needed. The online version will also have the best functionality and graphical display.\nThis document will continue to be updated regularly and publishing using the GitHub Repository. Please refresh this manual every time you open it to ensure you are viewing the most recent version.\nGuidance was last updated: 15 October, 2024.", "crumbs": [ "Introduction" ] @@ -54,7 +54,7 @@ "href": "content/workflow/metadata_sciencebase_first.html", "title": "Metadata From ScienceBase", "section": "", - "text": "Follow this workflow if you are creating mdJSON for the first time and already have project or product metadata on ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Adjust settings\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n4. Create or import contacts\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n5. Import projects\nFor importing metadata for a project of an existing ScienceBase project, import the ScienceBase record to create a new mdEditor record using the sbJSON Import.\n\n\n6. Import products\nFor importing metadata for a product of an existing ScienceBase product record, import the ScienceBase record to create a new mdEditor record using the sbJSON Import.\n\n\n7. Create or import data dictionaries\nIf a product record have a need for data dictionaries, create or import one.\n\n\n8. Complete metadata\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n9. Create associations\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.\n\n\n13. Consult QA/QC resources.\nSee the QA/QC Fixes page for suggestions about updating your data to check your metadata.", + "text": "Follow this workflow if you are creating mdJSON for the first time and already have project or product metadata on ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Adjust settings\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n4. Create or import contacts\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n5. Import projects\nFor importing metadata for a project of an existing ScienceBase project, import the ScienceBase record to create a new mdEditor record using the sbJSON Import.\n\n\n6. Import products\nFor importing metadata for a product of an existing ScienceBase product record, import the ScienceBase record to create a new mdEditor record using the sbJSON Import.\n\n\n7. Create or import data dictionaries\nIf a product record have a need for data dictionaries, create or import one.\n\n\n8. Complete metadata\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n9. Create associations\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.", "crumbs": [ "Workflow", "Metadata From ScienceBase" @@ -65,7 +65,7 @@ "href": "content/workflow/metadata_editing_republishing.html", "title": "Metadata Editing / Re-Publishing", "section": "", - "text": "Follow this workflow if you have already created and published mdJSON to ScienceBase and need to update the metadata and re-publish to ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Import mdEditor file(s).\nSelect and import the mdEditor file(s) that you wish to edit. Remember, once you have edited and published metadata from mdEditor, you must always use mdEditor to update the metadata (rather than make changes directly on ScienceBase). The Science Catalog will only update based on what is in mdJSON (and not sbJSON).\n\n\n4. Check the Settings\nEnsure the correct settings are in place for Importing, Metadata Repositories, and Publishing.\n\n\n5. Update Contacts\nUpdate or create new contacts using the Contacts entry form in mdEditor. After Contacts are created, they can be associated with project and product metadata records.\n\n\n6. Update Projects\nIf you have already created an mdEditor record for the product, update and edit metadata as needed using the Projects records editing interface.\n\n\n7. Update Products\nIf you have already created an mdEditor record for the product, update and edit metadata as needed using the Products records editing interface.\n\n\n8. Create or import data dictionaries\nIf a product record has a need for data dictionaries, create or import one.\n\n\n9. Check Associations between Projects and/or Products.\nIf you only updated metadata in existing record that were already associated, you do not need to do anything with the associations.\nIf you created a new product for your project, then associate those records in mdEditor. Associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\nCheck that your record published where expected and that the mdJSON and xml files are attached to the SB Item. Your records should publish to their existing locations. If you added a new product to a project, then it should appear as a new child item to the project.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.\n\n\n13. Consult QA/QC resources.\nSee the QA/QC Fixes page for suggestions about updating your data to check your metadata.", + "text": "Follow this workflow if you have already created and published mdJSON to ScienceBase and need to update the metadata and re-publish to ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Import mdEditor file(s).\nSelect and import the mdEditor file(s) that you wish to edit. Remember, once you have edited and published metadata from mdEditor, you must always use mdEditor to update the metadata (rather than make changes directly on ScienceBase). The Science Catalog will only update based on what is in mdJSON (and not sbJSON).\n\n\n4. Check the Settings\nEnsure the correct settings are in place for Importing, Metadata Repositories, and Publishing.\n\n\n5. Update Contacts\nUpdate or create new contacts using the Contacts entry form in mdEditor. After Contacts are created, they can be associated with project and product metadata records.\n\n\n6. Update Projects\nIf you have already created an mdEditor record for the product, update and edit metadata as needed using the Projects records editing interface.\n\n\n7. Update Products\nIf you have already created an mdEditor record for the product, update and edit metadata as needed using the Products records editing interface.\n\n\n8. Create or import data dictionaries\nIf a product record has a need for data dictionaries, create or import one.\n\n\n9. Check Associations between Projects and/or Products.\nIf you only updated metadata in existing record that were already associated, you do not need to do anything with the associations.\nIf you created a new product for your project, then associate those records in mdEditor. Associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\nCheck that your record published where expected and that the mdJSON and xml files are attached to the SB Item. Your records should publish to their existing locations. If you added a new product to a project, then it should appear as a new child item to the project.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.", "crumbs": [ "Workflow", "Metadata Editing / Re-Publishing" @@ -633,7 +633,7 @@ "href": "content/metadata_requirements.html", "title": "Metadata Requirements", "section": "", - "text": "Metadata fields have different requirements for Project and Product records.\n       Required: required for all records of that type.\n       If Applicable: required if the information is applicable and available.\n       Best Practice: recommended, but not required.\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nBasic Information\n\n\n\n\n       Title\nRequired*\nRequired*\n\n\n       Status\nRequired*\nRequired*\n\n\nDefault Locale\nRequired\nRequired\n\n\nResource Type\nRequired\nRequired\n\n\nPoints of Contact (multiple)\nRequired\nRequired\n\n\nCitation\n\n\n\n\n       Title\nRequired*\nRequired*\n\n\n       Dates (multiple)\nRequired*\nIf Applicable\n\n\n       Responsible Parties (multiple)\nRequired*\nRequired*\n\n\n       Online Resource\n\n\n\n\n              Name\nIf Applicable\nIf Applicable\n\n\n              URL\nIf Applicable\nIf Applicable\n\n\n              Function\nIf Applicable\nIf Applicable\n\n\n       Identifier\n\n\n\n\n              Identifier\nRequired\nRequired\n\n\n              Namespace\nRequired\nRequired\n\n\nDescription\n\n\n\n\n       Abstract\nRequired*\nRequired*\n\n\nTime Period\n\n\n\n\n       Start Date\nRequired*\nIf Applicable\n\n\n       End Date\nRequired*\nRequired*\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nMetadata Status\nRequired\nRequired\n\n\nDates\nRequired\n\n\n\nMetadata Contacts\n\n\n\n\n       Author\nRequired\nRequired\n\n\n       Publisher\nRequired\nRequired\n\n\n       Point of Contact\nRequired\nRequired\n\n\nMetadata Identifier\nRequired\nRequired\n\n\nParent Metadata\nRequired\nRequired\n\n\nMetadata Repositories\nRequired\nRequired\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nISO Topic Category\nRequired\n\n\n\nRequired\n\n\n\n\nSA Priority Area\nRequired\nRequired\n\n\nSA Science Topic\nRequired\nRequired\n\n\nConservation Action Open Standard\nIf Applicable\nIf Applicable\n\n\nGlobal Change Master Directory (GCMD)\nBest Practice\nBest Practice\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nExtent\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nTaxonomic System\nIf Applicable\nIf Applicable\n\n\nTaxonomic Classification\nIf Applicable\nIf Applicable\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nDistributor\n\n\n\n\n       Contacts\n\nIf Applicable\n\n\n       Role\n\nIf Applicable\n\n\nTransfer Options\n\n\n\n\n       Online Options\n\n\n\n\n              Name\n\nIf Applicable\n\n\n              URI\n\nIf Applicable\n\n\n              Function\n\nIf Applicable\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nConstraint Type\n\nRequired\n\n\nLegal\n\n\n\n\n       Access Constraints\n\nRequired\n\n\n       Use Constraints\n\nIf Applicable\n\n\nSecurity\n\n\n\n\n       Classification\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nAllocation\n\n\n\n\n       Amount\nRequired*\n\n\n\n       Currency\nRequired*\n\n\n\n       Award ID\nRequired*\n\n\n\n       Source\nRequired*\n\n\n\n       Recipient\nRequired\n\n\n\n       Other Contacts (multiple)\nRequired\n\n\n\n       Marked Funds\nIf Applicable\n\n\n\nTime Period\n\n\n\n\n       Dates\nRequired*\n\n\n\nDescription (multiple)\nBest Practice\n\n\n\n\n*Also required under the ScienceBase 30-day Policy", + "text": "Metadata fields have different requirements for Project and Product records.\n       Required: required for all records of that type.\n       If Applicable: required if the information is applicable and available.\n       Best Practice: recommended, but not required.\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nBasic Information\n\n\n\n\n       Title\nRequired\nRequired\n\n\n       Status\nRequired\nRequired\n\n\nDefault Locale\nRequired\nRequired\n\n\nResource Type\nRequired\nRequired\n\n\nPoints of Contact (multiple)\nRequired\nRequired\n\n\nCitation\n\n\n\n\n       Title\nRequired\nRequired\n\n\n       Dates (multiple)\nRequired\nIf Applicable\n\n\n       Responsible Parties (multiple)\nRequired\nRequired\n\n\n       Online Resource\n\n\n\n\n              Name\nIf Applicable\nIf Applicable\n\n\n              URL\nIf Applicable\nIf Applicable\n\n\n              Function\nIf Applicable\nIf Applicable\n\n\n       Identifier\n\n\n\n\n              Identifier\nRequired\nRequired\n\n\n              Namespace\nRequired\nRequired\n\n\nDescription\n\n\n\n\n       Abstract\nRequired\nRequired\n\n\nTime Period\n\n\n\n\n       Start Date\nRequired\nIf Applicable\n\n\n       End Date\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nMetadata Status\nRequired\nRequired\n\n\nDates\nRequired\n\n\n\nMetadata Contacts\n\n\n\n\n       Author\nRequired\nRequired\n\n\n       Publisher\nRequired\nRequired\n\n\n       Point of Contact\nRequired\nRequired\n\n\nMetadata Identifier\nRequired\nRequired\n\n\nParent Metadata\nRequired\nRequired\n\n\nMetadata Repositories\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nISO Topic Category\nRequired\n\n\n\nRequired\n\n\n\n\nSA Priority Area\nRequired\nRequired\n\n\nSA Science Topic\nRequired\nRequired\n\n\nConservation Action Open Standard\nIf Applicable\nIf Applicable\n\n\nGlobal Change Master Directory (GCMD)\nBest Practice\nBest Practice\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nExtent\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nTaxonomic System\nIf Applicable\nIf Applicable\n\n\nTaxonomic Classification\nIf Applicable\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nDistributor\n\n\n\n\n       Contacts\n\nIf Applicable\n\n\n       Role\n\nIf Applicable\n\n\nTransfer Options\n\n\n\n\n       Online Options\n\n\n\n\n              Name\n\nIf Applicable\n\n\n              URI\n\nIf Applicable\n\n\n              Function\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nConstraint Type\n\nRequired\n\n\nLegal\n\n\n\n\n       Access Constraints\n\nRequired\n\n\n       Use Constraints\n\nIf Applicable\n\n\nSecurity\n\n\n\n\n       Classification\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nAllocation\n\n\n\n\n       Amount\nRequired\n\n\n\n       Currency\nRequired\n\n\n\n       Award ID\nRequired\n\n\n\n       Source\nRequired\n\n\n\n       Recipient\nRequired\n\n\n\n       Other Contacts (multiple)\nRequired\n\n\n\n       Marked Funds\nIf Applicable\n\n\n\nTime Period\n\n\n\n\n       Dates\nRequired\n\n\n\nDescription (multiple)\nBest Practice", "crumbs": [ "Metadata Requirements" ] @@ -2278,7 +2278,7 @@ "href": "content/project_records/main_tab_project.html#citation", "title": "Main Tab", "section": "Citation", - "text": "Citation\nThe Citation describes pertinent information about your project such as: responsible parties, internal and ScienceBase identifiers, and any online resources that may relate to your item. The citation, much like a peer-reviewed publication citation, provides credit and services as a reference citation. Adding information in the citation will also improve users’ ability to find your items.\n\nTitle (Required)\nThe citation Title is automatically populated with the Basis Information section’s Title.\n\n\nAlternate Title (If desired)\nYou can add an Alternate Title, if desired. Generally these should be shorter than the full Title.\n\n\nDates (Required)\nEnter Dates for acquisition, creation, updated, or revision from the pick list and then enter the date. At least one of these date types is required.\n\n\nResponsible Parties (Required)\nResponsible parties must include the principal investigator of the project, but may optionally include other responsible parties such as funders (your region and program), partners, collaborators, and contributors. Collaborators could be intellectual participants while contributors could be intellectual and financial participants.\n\n\n\n\n\n\nNote\n\n\n\nTo add contacts to a metadata record, you must first create/upload the contacts in mdEditor. See the Contacts section for more information.\n\n\n\n\n\n\n\n\n\n\nRole\nContact\nRequirements\n\n\n\n\nprincipalInvestigator\nProject Principal Investigator\nRequired\n\n\ncoPrincipalInvestigator\nCo-Investigators\nRequired, if applicable\n\n\n\n\n\n\nOnline Resource (If applicable)\nEnter the Name, URL, and Function for the project homepage website, if available.\n\n\nIdentifier (Required)\nYou may enter as many Identifiers as desired. The identifier for the repository is required here. If you have other internal IDs for projects, enter them here. Other optional identifiers for projects include: Archive Folder Name.\n\n\n\n\n\n\nBest Practice\n\n\n\nCreate and use internal identifiers that are unique within your region or program for projects and their products. Example: GNLCC2010-11.\n\n\n\n\n\n\n\n\nNote\n\n\n\nIf your item does not have a ScienceBase ID yet, ScienceBase will create one automatically upon publishing. If you imported your item from ScienceBase originally, then the SBID will already be included in Metadata/Metadata Identifier and you do not need to include it here. Note that if you edit an item that is already on ScienceBase without using its existing ID, a duplicate item will be created on ScienceBase. Consult the Publish section of this manual to learn more.\n\n\n\n\n\nExample Citation in mdEditor", + "text": "Citation\nThe Citation describes pertinent information about your project such as: responsible parties, internal and ScienceBase identifiers, and any online resources that may relate to your item. The citation, much like a peer-reviewed publication citation, provides credit and services as a reference citation. Adding information in the citation will also improve users’ ability to find your items.\n\nTitle (Required)\nThe citation Title is automatically populated with the Basis Information section’s Title.\n\n\nAlternate Title\nYou can add an Alternate Title, if desired. Generally these should be shorter than the full Title.\n\n\nDates (Required)\nEnter Dates for acquisition, creation, updated, or revision from the pick list and then enter the date. At least one of these date types is required.\n\n\nResponsible Parties (Required)\nResponsible parties must include the principal investigator of the project, but may optionally include other responsible parties such as funders (your region and program), partners, collaborators, and contributors. Collaborators could be intellectual participants while contributors could be intellectual and financial participants.\n\n\n\n\n\n\nNote\n\n\n\nTo add contacts to a metadata record, you must first create/upload the contacts in mdEditor. See the Contacts section for more information.\n\n\n\n\n\n\n\n\n\n\nRole\nContact\nRequirements\n\n\n\n\nprincipalInvestigator\nProject Principal Investigator\nRequired\n\n\ncoPrincipalInvestigator\nCo-Investigators\nIf applicable\n\n\n\n\n\n\nOnline Resource (If applicable)\nEnter the Name, URL, and Function for the project homepage website, if available.\n\n\nIdentifier (Required)\nYou may enter as many Identifiers as desired. The identifier for the repository is required here. If you have other internal IDs for projects, enter them here. Other optional identifiers for projects include: Archive Folder Name.\n\n\n\n\n\n\nBest Practice\n\n\n\nCreate and use internal identifiers that are unique within your region or program for projects and their products. Example: GNLCC2010-11.\n\n\n\n\n\n\n\n\nNote\n\n\n\nIf your item does not have a ScienceBase ID yet, ScienceBase will create one automatically upon publishing. If you imported your item from ScienceBase originally, then the SBID will already be included in Metadata/Metadata Identifier and you do not need to include it here. Note that if you edit an item that is already on ScienceBase without using its existing ID, a duplicate item will be created on ScienceBase. Consult the Publish section of this manual to learn more.\n\n\n\n\n\nExample Citation in mdEditor", "crumbs": [ "Project Records", "Main Tab" @@ -2462,7 +2462,7 @@ "href": "content/workflow/metadata_from_scratch.html", "title": "Metadata From Scratch", "section": "", - "text": "Follow this workflow if you are creating mdJSON metadata for the very first time and you do not have existing project or product metadata already on ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA National Data Steward.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Adjust settings\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n4. Create or import contacts\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the mdEditor Seed Contacts that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward.\n\n\n5. Create projects\nFor creating metadata for a project you will need to create an mdEditor project record from scratch.\nOn the main page’s left menu-bar next to “Metadata Records” click on the plus (+) sign to add a new record.\n\nFill in the rest of the information in main tab, as needed.\n\n\n6. Create products\nFor creating metadata for a product you will need to create an mdEditor product record from scratch.\nOn the main page’s left menu-bar next to “Metadata Records” click on the plus (+) sign to add a new record.\n\nFill in the rest of the information in main tab, as needed.\n\n\n7. Create or import data dictionaries\nIf a product record have a need for data dictionaries, create or import one.\n\n\n8. Complete metadata\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n9. Create associations\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.\n\n\n13. Consult QA/QC resources.\nSee the QA/QC Fixes page for suggestions about updating your data to check your metadata.", + "text": "Follow this workflow if you are creating mdJSON metadata for the very first time and you do not have existing project or product metadata already on ScienceBase.\n\n1. Gather information\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA National Data Steward.\n\n\n2. Open mdEditor\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n3. Adjust settings\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n4. Create or import contacts\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the mdEditor Seed Contacts that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward.\n\n\n5. Create projects\nFor creating metadata for a project you will need to create an mdEditor project record from scratch.\nOn the main page’s left menu-bar next to “Metadata Records” click on the plus (+) sign to add a new record.\n\nFill in the rest of the information in main tab, as needed.\n\n\n6. Create products\nFor creating metadata for a product you will need to create an mdEditor product record from scratch.\nOn the main page’s left menu-bar next to “Metadata Records” click on the plus (+) sign to add a new record.\n\nFill in the rest of the information in main tab, as needed.\n\n\n7. Create or import data dictionaries\nIf a product record have a need for data dictionaries, create or import one.\n\n\n8. Complete metadata\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n9. Create associations\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n10. Publish your records\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n11. Export your records\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n12. Review Science Catalog\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.", "crumbs": [ "Workflow", "Metadata From Scratch" @@ -2473,7 +2473,7 @@ "href": "content/workflow/workflow_overview.html", "title": "Workflow: Overview", "section": "", - "text": "The following is a suggested workflow for using mdEditor to create, publish, and save metadata records for SA projects and products.\n\n\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n\nFor creating or importing metadata for a project use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase project records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase project record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the project, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nFor creating or importing metadata for a product use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase product records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase product record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the product, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nIf a product record has a need for data dictionaries, create or import one.\n\n\n\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.\n\n\n\nSee the QA/QC Fixes page for suggestions about updating your data to check your metadata.", + "text": "The following is a suggested workflow for using mdEditor to create, publish, and save metadata records for SA projects and products.\n\n\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n\nFor creating or importing metadata for a project use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase project records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase project record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the project, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nFor creating or importing metadata for a product use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase product records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase product record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the product, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nIf a product record has a need for data dictionaries, create or import one.\n\n\n\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.", "crumbs": [ "Workflow" ] @@ -2483,7 +2483,7 @@ "href": "content/workflow/workflow_overview.html#suggested-workflow-for-sa-metadata-and-mdeditor", "title": "Workflow: Overview", "section": "", - "text": "The following is a suggested workflow for using mdEditor to create, publish, and save metadata records for SA projects and products.\n\n\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n\nFor creating or importing metadata for a project use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase project records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase project record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the project, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nFor creating or importing metadata for a product use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase product records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase product record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the product, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nIf a product record has a need for data dictionaries, create or import one.\n\n\n\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.\n\n\n\nSee the QA/QC Fixes page for suggestions about updating your data to check your metadata.", + "text": "The following is a suggested workflow for using mdEditor to create, publish, and save metadata records for SA projects and products.\n\n\nHave information about your contacts, projects, and products on hand before you begin creating metadata records. Key information to gather includes project proposals, funding agreements and amounts, project reports, product information, and contact information for individuals and organizations involved in the projects.\n\n\n\nThe direct link to mdEditor is https://go.mdeditor.org. Choose the browser you plan to use for mdEditor and bookmark this link.\nmdEditor can also be accessed from its homepage at https://www.mdeditor.org/. This site provides some background information and Frequently Asked Questions about mdEditor.\nAlways hit Refresh in your browser before each work session (and periodically throughout the session) to ensure that you are using the most updated version of mdEditor.\n\n\n\nIn mdEditor settings, set the SA-specific settings for importing from ScienceBase, Metadata Repositories, and Publishing (See Settings).\n\n\n\nContacts must be created or uploaded before they can be added to project and product metadata records using the Contacts entry form in mdEditor.\nUse the “contacts seed file” that contains pre-filled information and standard naming conventions for all SA regions, common federal agencies, and the SA Network Data Steward. (link to contact seed file here)\n\n\n\nFor creating or importing metadata for a project use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase project records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase project record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the project, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nFor creating or importing metadata for a product use one of the following options based on whether or not you have already created a mdEditor project record.\n\nIf you do not have existing ScienceBase product records, create an mdEditor project record from scratch using the Metadata from Scratch workflow.\nIf you have an existing ScienceBase product record that has not been edited in mdEditor, import the ScienceBase record to create a new mdEditor record using the Metadata from ScienceBase workflow.\nIf you have already created an mdEditor record for the product, import the mdEditor file to Metadata Editing / Re-Publishing workflow to continue editing.\n\n\n\n\nIf a product record has a need for data dictionaries, create or import one.\n\n\n\nDecide on your desired file management approach and complete your metadata accordingly. See the File Management section for options and instructions.\n\n\n\nFor projects and/or products, associations can be either associated from a project or associated from a product.\n\n\n\nFrom the mdEditor interface, publish the records to ScienceBase.\n\n\n\nUse the Export function to export records of your products, projects, and contacts for backup, transfer, or sharing. You may want to export working backups before publishing depending on your situation, but archival exports should be done after publishing since publishing can alter records, like adding or changing a ScienceBase ID.\n\n\n\nThe SA Science Catalog updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks.", "crumbs": [ "Workflow" ] @@ -2646,7 +2646,7 @@ "href": "content/metadata_requirements.html#projects-and-products", "title": "Metadata Requirements", "section": "", - "text": "Metadata fields have different requirements for Project and Product records.\n       Required: required for all records of that type.\n       If Applicable: required if the information is applicable and available.\n       Best Practice: recommended, but not required.\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nBasic Information\n\n\n\n\n       Title\nRequired*\nRequired*\n\n\n       Status\nRequired*\nRequired*\n\n\nDefault Locale\nRequired\nRequired\n\n\nResource Type\nRequired\nRequired\n\n\nPoints of Contact (multiple)\nRequired\nRequired\n\n\nCitation\n\n\n\n\n       Title\nRequired*\nRequired*\n\n\n       Dates (multiple)\nRequired*\nIf Applicable\n\n\n       Responsible Parties (multiple)\nRequired*\nRequired*\n\n\n       Online Resource\n\n\n\n\n              Name\nIf Applicable\nIf Applicable\n\n\n              URL\nIf Applicable\nIf Applicable\n\n\n              Function\nIf Applicable\nIf Applicable\n\n\n       Identifier\n\n\n\n\n              Identifier\nRequired\nRequired\n\n\n              Namespace\nRequired\nRequired\n\n\nDescription\n\n\n\n\n       Abstract\nRequired*\nRequired*\n\n\nTime Period\n\n\n\n\n       Start Date\nRequired*\nIf Applicable\n\n\n       End Date\nRequired*\nRequired*\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nMetadata Status\nRequired\nRequired\n\n\nDates\nRequired\n\n\n\nMetadata Contacts\n\n\n\n\n       Author\nRequired\nRequired\n\n\n       Publisher\nRequired\nRequired\n\n\n       Point of Contact\nRequired\nRequired\n\n\nMetadata Identifier\nRequired\nRequired\n\n\nParent Metadata\nRequired\nRequired\n\n\nMetadata Repositories\nRequired\nRequired\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nISO Topic Category\nRequired\n\n\n\nRequired\n\n\n\n\nSA Priority Area\nRequired\nRequired\n\n\nSA Science Topic\nRequired\nRequired\n\n\nConservation Action Open Standard\nIf Applicable\nIf Applicable\n\n\nGlobal Change Master Directory (GCMD)\nBest Practice\nBest Practice\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nExtent\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nTaxonomic System\nIf Applicable\nIf Applicable\n\n\nTaxonomic Classification\nIf Applicable\nIf Applicable\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nDistributor\n\n\n\n\n       Contacts\n\nIf Applicable\n\n\n       Role\n\nIf Applicable\n\n\nTransfer Options\n\n\n\n\n       Online Options\n\n\n\n\n              Name\n\nIf Applicable\n\n\n              URI\n\nIf Applicable\n\n\n              Function\n\nIf Applicable\n\n\n\n*Also required under the ScienceBase 30-day Policy\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nConstraint Type\n\nRequired\n\n\nLegal\n\n\n\n\n       Access Constraints\n\nRequired\n\n\n       Use Constraints\n\nIf Applicable\n\n\nSecurity\n\n\n\n\n       Classification\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nAllocation\n\n\n\n\n       Amount\nRequired*\n\n\n\n       Currency\nRequired*\n\n\n\n       Award ID\nRequired*\n\n\n\n       Source\nRequired*\n\n\n\n       Recipient\nRequired\n\n\n\n       Other Contacts (multiple)\nRequired\n\n\n\n       Marked Funds\nIf Applicable\n\n\n\nTime Period\n\n\n\n\n       Dates\nRequired*\n\n\n\nDescription (multiple)\nBest Practice\n\n\n\n\n*Also required under the ScienceBase 30-day Policy", + "text": "Metadata fields have different requirements for Project and Product records.\n       Required: required for all records of that type.\n       If Applicable: required if the information is applicable and available.\n       Best Practice: recommended, but not required.\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nBasic Information\n\n\n\n\n       Title\nRequired\nRequired\n\n\n       Status\nRequired\nRequired\n\n\nDefault Locale\nRequired\nRequired\n\n\nResource Type\nRequired\nRequired\n\n\nPoints of Contact (multiple)\nRequired\nRequired\n\n\nCitation\n\n\n\n\n       Title\nRequired\nRequired\n\n\n       Dates (multiple)\nRequired\nIf Applicable\n\n\n       Responsible Parties (multiple)\nRequired\nRequired\n\n\n       Online Resource\n\n\n\n\n              Name\nIf Applicable\nIf Applicable\n\n\n              URL\nIf Applicable\nIf Applicable\n\n\n              Function\nIf Applicable\nIf Applicable\n\n\n       Identifier\n\n\n\n\n              Identifier\nRequired\nRequired\n\n\n              Namespace\nRequired\nRequired\n\n\nDescription\n\n\n\n\n       Abstract\nRequired\nRequired\n\n\nTime Period\n\n\n\n\n       Start Date\nRequired\nIf Applicable\n\n\n       End Date\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nMetadata Status\nRequired\nRequired\n\n\nDates\nRequired\n\n\n\nMetadata Contacts\n\n\n\n\n       Author\nRequired\nRequired\n\n\n       Publisher\nRequired\nRequired\n\n\n       Point of Contact\nRequired\nRequired\n\n\nMetadata Identifier\nRequired\nRequired\n\n\nParent Metadata\nRequired\nRequired\n\n\nMetadata Repositories\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nISO Topic Category\nRequired\n\n\n\nRequired\n\n\n\n\nSA Priority Area\nRequired\nRequired\n\n\nSA Science Topic\nRequired\nRequired\n\n\nConservation Action Open Standard\nIf Applicable\nIf Applicable\n\n\nGlobal Change Master Directory (GCMD)\nBest Practice\nBest Practice\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nExtent\nRequired\nRequired\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nTaxonomic System\nIf Applicable\nIf Applicable\n\n\nTaxonomic Classification\nIf Applicable\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nDistributor\n\n\n\n\n       Contacts\n\nIf Applicable\n\n\n       Role\n\nIf Applicable\n\n\nTransfer Options\n\n\n\n\n       Online Options\n\n\n\n\n              Name\n\nIf Applicable\n\n\n              URI\n\nIf Applicable\n\n\n              Function\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nConstraint Type\n\nRequired\n\n\nLegal\n\n\n\n\n       Access Constraints\n\nRequired\n\n\n       Use Constraints\n\nIf Applicable\n\n\nSecurity\n\n\n\n\n       Classification\n\nIf Applicable\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nMetadata Field\nProject Records\nProduct Records\n\n\n\n\nAllocation\n\n\n\n\n       Amount\nRequired\n\n\n\n       Currency\nRequired\n\n\n\n       Award ID\nRequired\n\n\n\n       Source\nRequired\n\n\n\n       Recipient\nRequired\n\n\n\n       Other Contacts (multiple)\nRequired\n\n\n\n       Marked Funds\nIf Applicable\n\n\n\nTime Period\n\n\n\n\n       Dates\nRequired\n\n\n\nDescription (multiple)\nBest Practice", "crumbs": [ "Metadata Requirements" ] @@ -2656,7 +2656,7 @@ "href": "content/metadata_requirements.html#contacts", "title": "Metadata Requirements", "section": "Contacts", - "text": "Contacts\nCertain metadata fields are required for Individual or Organization contacts.\n\nContacts Information\n\n\n\nMetadata Field\nIndividual\nOrganization\n\n\n\n\nType\nRequired\nRequired\n\n\nIndividual Name\nRequired\n\n\n\nOrganizational Name\n\nRequired\n\n\nPosition Name\nIf Applicable\n\n\n\nContact Type\nRequired\nRequired\n\n\nMember Organization\nRequired\n\n\n\nEmail Address\nRequired\nRequired\n\n\nOnline Resource\n\nRequired\n\n\nPhysical Address\nBest Practice\nBest Practice\n\n\nLogo\n\nBest Practice", + "text": "Contacts\nCertain metadata fields are required for Individual or Organization contacts.\n\nContacts Information\n\n\n\n\n\n\n\n\nMetadata Field\nIndividual\nOrganization\n\n\n\n\nType\nRequired\nRequired\n\n\nIndividual Name\nRequired\n\n\n\nOrganizational Name\n\nRequired\n\n\nPosition Name\nIf Applicable\n\n\n\nContact Type\nRequired\nRequired\n\n\nMember Organization\nRequired\n\n\n\nEmail Address\nRequired\nRequired\n\n\nOnline Resource\n\nRequired\n\n\nPhysical Address\nBest Practice\nBest Practice\n\n\nLogo\n\nBest Practice", "crumbs": [ "Metadata Requirements" ] @@ -2795,7 +2795,7 @@ "href": "content/project_records/main_tab_project.html#points-of-contact-required", "title": "Main Tab", "section": "Points of Contact (Required)", - "text": "Points of Contact (Required)\nAdding a point of contact gives staff information on who to contact should they have a question regarding your project or product. From the Role drop-down menu, select pointOfContact. From the Contacts drop-down menu, select a contact from the list of contacts. See the Contact Records section for information on creating contacts.\nAdd additional Points of Contact as listed in the table below.\n\n\n\n\n\n\n\n\nRole\nContact\nRequirements\n\n\n\n\npointOfContact\nFWS Science Applications National Data Steward\nRequired\n\n\npointOfContact\nData Steward\nRequired\n\n\nprincipalInvestigator\nProject Principal Investigator and/or Producer\nRequired, if applicable\n\n\ncustodian\nData Custodian\nRequired, if applicable\n\n\nowner\nData Trustee\nRequired\n\n\nadministrator\nProject Officer, if not the Steward\nRequired\n\n\nadministrator\nFWS Region (legacy and DOI Unified), FWS Program\nRequired\n\n\ncollaborator\nPartnership Organizations and/or Programs\nRequired, if applicable\n\n\n\n\n\n\n\nExample Points of Contact Entry in mdEditor\n\n\n\n\n\n\n\n\nNote\n\n\n\nThe FWS Science Applications National Data Steward will serve as the long term contact and backup. This way, users have a point-of-contact even if there is a positional change within an organization. Regional Data Steward should be included in addition as a point of contact, if available.", + "text": "Points of Contact (Required)\nAdding a point of contact gives staff information on who to contact should they have a question regarding your project or product. From the Role drop-down menu, select pointOfContact. From the Contacts drop-down menu, select a contact from the list of contacts. See the Contact Records section for information on creating contacts.\nAdd additional Points of Contact as listed in the table below.\n\n\n\n\n\n\n\n\nRole\nContact\nRequirements\n\n\n\n\npointOfContact\nFWS Science Applications National Data Steward\nRequired\n\n\npointOfContact\nData Steward\nRequired\n\n\nprincipalInvestigator\nProject Principal Investigator and/or Producer\nIf applicable\n\n\ncustodian\nData Custodian\nIf applicable\n\n\nowner\nData Trustee\nRequired\n\n\nadministrator\nProject Officer, if not the Steward\nRequired\n\n\nadministrator\nFWS Region (legacy and DOI Unified), FWS Program\nRequired\n\n\ncollaborator\nPartnership Organizations and/or Programs\nIf applicable\n\n\n\n\n\n\n\nExample Points of Contact Entry in mdEditor\n\n\n\n\n\n\n\n\nNote\n\n\n\nThe FWS Science Applications National Data Steward will serve as the long term contact and backup. This way, users have a point-of-contact even if there is a positional change within an organization. Regional Data Steward should be included in addition as a point of contact, if available.", "crumbs": [ "Project Records", "Main Tab" @@ -2890,7 +2890,7 @@ "href": "content/science_catalog.html#sa-science-catalog-and-mdeditor", "title": "SA Science Catalog", "section": "SA Science Catalog and mdEditor", - "text": "SA Science Catalog and mdEditor\nThis sections shows the elements in the SA Science Catalog and where they are derived in mdEditor. Items will only show up in SA Science Catalog when they have the proper metadata repositories designation (Projects and Products) and have been published to ScienceBase.\n\nSA Science Catalog and mdEditor Fields Crosswalk Table\n\n\n\nSA Science Catalog\nmdEditor Project Item\nmdEditor Product Item\n\n\n\n\nResource Type\nMain Tab: Resource Type\nMain Tab: Resource Type\n\n\nTitle\nMain Tab: Title\nMain Tab: Title\n\n\nSource\nScienceBase folder location1\nScienceBase folder location1\n\n\nFiscal Years Funded\nFunding Tab: Allocation: Time Period: Dates\nAssociated Project2\n\n\nLast Update Date\nMain Tab: Citation: Dates\nMain Tab: Citation: Dates\n\n\nStatus\nMain Tab: Status\nMain Tab: Status\n\n\nProject Dates (multiple)\nMain Tab: Citation: Dates\nMain Tab: Citation: Dates\n\n\nKeywords\nKeywords Tab\nKeywords Tab\n\n\nContacts\nMain Tab: Points of Contact\nContacts\n\n\nFunding\nFunding Tab: Allocation\n\n\n\nTaxonomy\nTaxonomy Tab\nTaxonomy Tab\n\n\n\n\n1 Items in ScienceBase’s USFWS Community are designated as “FWS ScienceBase Community”. Items in ScienceBase’s LCC Community are designated based on their top-level Science Applications Region folder’s name.\n2 For a Product item, the Fiscal Year is derived from the associated Project item.\n\n\n\n\n\n\n\nNote\n\n\n\nThe SA Science Catalog entries are displayed in descending order of Last Update Date.", + "text": "SA Science Catalog and mdEditor\nThis sections shows the elements in the SA Science Catalog and where they are derived in mdEditor. Items will only show up in SA Science Catalog when they have the proper metadata repositories designation (Projects and Products) and have been published to ScienceBase.\n\nSA Science Catalog and mdEditor Fields Crosswalk Table\n\n\n\nSA Science Catalog\nmdEditor Project Item\nmdEditor Product Item\n\n\n\n\nResource Type\nMain Tab: Resource Type\nMain Tab: Resource Type\n\n\nTitle\nMain Tab: Title\nMain Tab: Title\n\n\nSource\nScienceBase folder location1\nScienceBase folder location1\n\n\nFiscal Years Funded\nFunding Tab: Funding Period: Time Period: Dates\nAssociated Project2\n\n\nLast Update Date\nMain Tab: Citation: Dates\nMain Tab: Citation: Dates\n\n\nStatus\nMain Tab: Status\nMain Tab: Status\n\n\nProject Dates (multiple)\nMain Tab: Citation: Dates\nMain Tab: Citation: Dates\n\n\nKeywords\nKeywords Tab\nKeywords Tab\n\n\nContacts\nMain Tab: Points of Contact\nContacts\n\n\nFunding\nFunding Tab: Allocation\n\n\n\nTaxonomy\nTaxonomy Tab\nTaxonomy Tab\n\n\n\n\n1 Items in ScienceBase’s USFWS Community are designated as “FWS ScienceBase Community”. Items in ScienceBase’s LCC Community are designated based on their top-level Science Applications Region folder’s name.\n2 For a Product item, the Fiscal Year is derived from the associated Project item.\n\n\n\n\n\n\n\nNote\n\n\n\nThe SA Science Catalog entries are displayed in descending order of Last Update Date.", "crumbs": [ "SA Science Catalog" ] @@ -3003,5 +3003,16 @@ "Appendix", "Non-Duplication Policy" ] + }, + { + "objectID": "content/project_records/metadata_tab_project.html#parent-metadata-required", + "href": "content/project_records/metadata_tab_project.html#parent-metadata-required", + "title": "Metadata Tab", + "section": "Parent Metadata (Required)", + "text": "Parent Metadata (Required)\nParent Metadata tells mdEditor where the project metadata should go when it is published. If using ScienceBase, this is the folder above the project by default.\nIf you imported the project metadata from ScienceBase originally, this section will be populated already.\nIf you created the project metadata from scratch in mdEditor, this will be blank. If you provide a default parent ID in Settings (Publishing Settings for ScienceBase), this will be generated for you when when you publish. This is most likely your SA regional project folder. You can enter the parent item SBID directly in your individual metadata record if you wish.\n\nTitle (Required)\nIf the Title is not already populated, you can enter something like “Parent Folder”.\n\n\nIdentifier and Namespace (Required)\nThe Identifier and Namespace defines the location of the parent folder in ScienceBase.\n\nThe ScienceBase identifier is the alphanumeric string in the item’s URL immediately following “item/“. For example, 66326aebd34ea70bd5f26d62 is the SBID for the item at the URL: https://www.sciencebase.gov/catalog/item/66326aebd34ea70bd5f26d62\n\n\n\n\nExample ScienceBase Parent Metadata entry", + "crumbs": [ + "Project Records", + "Metadata Tab" + ] } ] \ No newline at end of file diff --git a/_site/sitemap.xml b/_site/sitemap.xml index 6982f5c..3526494 100644 --- a/_site/sitemap.xml +++ b/_site/sitemap.xml @@ -302,7 +302,7 @@ https://usfws.github.io/Science_Applications_Metadata_Guidance/index.html - 2024-10-15T12:49:32.537Z + 2024-10-15T19:19:54.307Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/cofunded_project_protocols/cofunded_projects_overview.html @@ -330,11 +330,11 @@ https://usfws.github.io/Science_Applications_Metadata_Guidance/content/project_records/main_tab_project.html - 2024-10-15T13:42:46.529Z + 2024-10-15T20:06:25.399Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/roles_and_responsibilities.html - 2024-07-30T16:37:58.406Z + 2024-10-15T19:20:32.794Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/appendix/appendix_overview.html @@ -358,23 +358,23 @@ https://usfws.github.io/Science_Applications_Metadata_Guidance/content/metadata_requirements.html - 2024-09-04T18:36:38.389Z + 2024-10-15T20:32:20.976Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/workflow/workflow_overview.html - 2024-07-30T16:37:58.422Z + 2024-10-15T19:36:13.558Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/workflow/metadata_from_scratch.html - 2024-07-30T16:37:58.422Z + 2024-10-15T19:36:35.370Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/workflow/metadata_sciencebase_first.html - 2024-08-06T17:19:21.470Z + 2024-10-15T19:36:23.069Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/workflow/metadata_editing_republishing.html - 2024-07-30T16:37:58.422Z + 2024-10-15T19:36:53.605Z https://usfws.github.io/Science_Applications_Metadata_Guidance/content/metadata_file_management/metadata_file_management_overview.html @@ -394,6 +394,14 @@ https://usfws.github.io/Science_Applications_Metadata_Guidance/content/project_records/metadata_tab_project.html - 2024-10-15T13:50:35.122Z + 2024-10-15T14:29:06.372Z + + + https://usfws.github.io/Science_Applications_Metadata_Guidance/content/science_catalog.html + 2024-10-15T19:28:23.927Z + + + https://usfws.github.io/Science_Applications_Metadata_Guidance/content/product_records/main_tab_product.html + 2024-10-15T20:08:57.095Z diff --git a/content/metadata_requirements.qmd b/content/metadata_requirements.qmd index 976b4c7..c1bd47d 100644 --- a/content/metadata_requirements.qmd +++ b/content/metadata_requirements.qmd @@ -19,15 +19,15 @@ Metadata fields have different requirements for **Project** and **Product** reco | Metadata Field | Project Records | Product Records | |:------------------------------|:-------------|:-------------| | Basic Information | | | -|        Title | [Required](project_records/main_tab_project.qmd#title-required)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#title)`r req_style`^\*^ | -|        Status | [Required](project_records/main_tab_project.qmd#status-required)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#status)`r req_style`^\*^ | +|        Title | [Required](project_records/main_tab_project.qmd#title-required)`r req_style` | [Required](product_records/main_tab_product.qmd#title)`r req_style` | +|        Status | [Required](project_records/main_tab_project.qmd#status-required)`r req_style` | [Required](product_records/main_tab_product.qmd#status)`r req_style` | | Default Locale | [Required](project_records/main_tab_project.qmd#default-locale-required)`r req_style` | [Required](product_records/main_tab_product.qmd#default-locale-required)`r req_style` | | Resource Type | [Required](project_records/main_tab_project.qmd#resource-types-required)`r req_style` | [Required](product_records/main_tab_product.qmd#resource-types-required)`r req_style` | | Points of Contact (multiple) | [Required](project_records/main_tab_project.qmd#points-of-contact-required)`r req_style` | [Required](product_records/main_tab_product.qmd#points-of-contact-required)`r req_style` | | Citation | | | -|        Title | [Required](project_records/main_tab_project.qmd#title-required-1)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#title)`r req_style`^\*^| -|        Dates (multiple) | [Required](project_records/main_tab_project.qmd#dates-required)`r req_style`^\*^ | [If Applicable](product_records/main_tab_product.qmd#dates-if-applicable)`r if_style` | -|        Responsible Parties (multiple) | [Required](project_records/main_tab_project.qmd#responsible-parties-required)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#responsible-parties-required)`r req_style`^\*^ | +|        Title | [Required](project_records/main_tab_project.qmd#title-required-1)`r req_style` | [Required](product_records/main_tab_product.qmd#title)`r req_style`| +|        Dates (multiple) | [Required](project_records/main_tab_project.qmd#dates-required)`r req_style` | [If Applicable](product_records/main_tab_product.qmd#dates-if-applicable)`r if_style` | +|        Responsible Parties (multiple) | [Required](project_records/main_tab_project.qmd#responsible-parties-required)`r req_style` | [Required](product_records/main_tab_product.qmd#responsible-parties-required)`r req_style` | |        Online Resource | | | |               Name | [If Applicable](project_records/main_tab_project.qmd#online-resource-if-applicable)`r if_style`| [If Applicable](product_records/main_tab_product.qmd#online-resource-if-applicable)`r if_style` | |               URL | [If Applicable](project_records/main_tab_project.qmd#online-resource-if-applicable)`r if_style`| [If Applicable](product_records/main_tab_product.qmd#online-resource-if-applicable)`r if_style` | @@ -36,13 +36,11 @@ Metadata fields have different requirements for **Project** and **Product** reco |               Identifier | [Required](project_records/main_tab_project.qmd#identifier-required)`r req_style` | [Required](product_records/main_tab_product.qmd#identifier-required)`r req_style` | |               Namespace | [Required](project_records/main_tab_project.qmd#namespace-required)`r req_style` | [Required](product_records/main_tab_product.qmd#namespace-required)`r req_style` | | Description | | | -|        Abstract | [Required](project_records/main_tab_project.qmd#abstract-required)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#abstract-required)`r req_style`^\*^ | +|        Abstract | [Required](project_records/main_tab_project.qmd#abstract-required)`r req_style` | [Required](product_records/main_tab_product.qmd#abstract-required)`r req_style` | | Time Period | | | -|        Start Date | [Required](project_records/main_tab_project.qmd#time-period)`r req_style`^\*^ | [If Applicable](product_records/main_tab_product.qmd#time-period)`r if_style` | -|        End Date | [Required](project_records/main_tab_project.qmd#time-period)`r req_style`^\*^ | [Required](product_records/main_tab_product.qmd#time-period)`r req_style`^\*^ | -: {.striped .hover .bordered .sm .allborder} - -^\*^Also required under the ScienceBase 30-day Policy +|        Start Date | [Required](project_records/main_tab_project.qmd#time-period)`r req_style` | [If Applicable](product_records/main_tab_product.qmd#time-period)`r if_style` | +|        End Date | [Required](project_records/main_tab_project.qmd#time-period)`r req_style` | [Required](product_records/main_tab_product.qmd#time-period)`r req_style` | +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"} ### Metadata Tab | Metadata Field | Project Records | Product Records | @@ -56,9 +54,8 @@ Metadata fields have different requirements for **Project** and **Product** reco | Metadata Identifier | [Required](project_records/metadata_tab_project.qmd#metadata-identifier-required)`r req_style` | [Required](product_records/metadata_tab_product.qmd#metadata-identifier-required)`r req_style`| | Parent Metadata | [Required](project_records/metadata_tab_project.qmd#parent-metadata-required)`r req_style` | [Required](product_records/metadata_tab_product.qmd#parent-metadata-required)`r req_style`| | Metadata Repositories | [Required](project_records/metadata_tab_project.qmd#metadata-repositories-required)`r req_style` | [Required](project_records/metadata_tab_project.qmd#metadata-repositories-required)`r req_style`| -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"} -^\*^Also required under the ScienceBase 30-day Policy
    ### Keywords Tab @@ -70,7 +67,7 @@ Metadata fields have different requirements for **Project** and **Product** reco | SA Science Topic | [Required](project_records/keywords_tab_project.qmd#science-topic-required)`r req_style` | [Required](product_records/keywords_tab_product.qmd#science-topic-required)`r req_style` | | Conservation Action Open Standard | [If Applicable](project_records/keywords_tab_project.qmd#conservation-action-open-standard-required-if-applicable)`r if_style` | [If Applicable](product_records/keywords_tab_product.qmd#conservation-action-open-standard-required-if-applicable)`r if_style` | | Global Change Master Directory (GCMD) | [Best Practice](project_records/keywords_tab_project.qmd#global-change-master-directory-gcmd-best-practice)`r best_style` | [Best Practice](product_records/keywords_tab_product.qmd#global-change-master-directory-gcmd-best-practice)`r best_style` | -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"}
    @@ -78,8 +75,8 @@ Metadata fields have different requirements for **Project** and **Product** reco | Metadata Field | Project Records | Product Records | |:------------------------------------|:----------|:----------| | Extent|[Required](project_records/extent_tab_project.qmd#add-taxonomic-system#creating-extents)`r req_style` | [Required](product_records/extent_tab_product.qmd#creating-extents)`r req_style` | -: {.striped .hover .bordered .sm .allborder} - +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"} +
    ### Taxonomy Tab @@ -87,7 +84,7 @@ Metadata fields have different requirements for **Project** and **Product** reco |:---------------------|:-------------------|:-------------------| | Taxonomic System |[If Applicable](project_records/taxonomy_tab_project.qmd#add-taxonomic-system)`r if_style` | [If Applicable](product_records/taxonomy_tab_product.qmd#add-taxonomic-system)`r if_style`| | Taxonomic Classification |[If Applicable](project_records/taxonomy_tab_project.qmd#add-taxonomic-system)`r if_style` | [If Applicable](product_records/taxonomy_tab_product.qmd#add-taxonomic-system)`r if_style`| -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"}
    @@ -102,9 +99,8 @@ Metadata fields have different requirements for **Project** and **Product** reco |               Name | | [If Applicable](product_records/distribution_tab_product.qmd#tname-if-applicable)`r if_style` | |               URI | | [If Applicable](product_records/distribution_tab_product.qmd#uri-if-applicable)`r if_style` | |               Function | | [If Applicable](product_records/distribution_tab_product.qmd#function-if-applicable)`r if_style` | -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"} -^\*^Also required under the ScienceBase 30-day Policy
    ### Constraints Tab @@ -116,7 +112,7 @@ Metadata fields have different requirements for **Project** and **Product** reco |        Use Constraints | | [If Applicable](product_records/constraints_tab_product.qmd#legal)`r if_style` | | Security | | | |        Classification | | [If Applicable](product_records/constraints_tab_product.qmd#security)`r if_style` | -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"}
    @@ -124,19 +120,18 @@ Metadata fields have different requirements for **Project** and **Product** reco | Metadata Field | Project Records | Product Records | |:------------------------------|:-------------|:-------------| | Allocation | | | -|        Amount | [Required](project_records/funding_tab_project.qmd#amount-required)`r req_style`^\*^ | | -|        Currency | [Required](project_records/funding_tab_project.qmd#currency-required)`r req_style`^\*^ | | -|        Award ID | [Required](project_records/funding_tab_project.qmd#award-id-required)`r req_style`^\*^ | | -|        Source | [Required](project_records/funding_tab_project.qmd#source-required)`r req_style`^\*^ | | +|        Amount | [Required](project_records/funding_tab_project.qmd#amount-required)`r req_style` | | +|        Currency | [Required](project_records/funding_tab_project.qmd#currency-required)`r req_style` | | +|        Award ID | [Required](project_records/funding_tab_project.qmd#award-id-required)`r req_style` | | +|        Source | [Required](project_records/funding_tab_project.qmd#source-required)`r req_style` | | |        Recipient | [Required](project_records/funding_tab_project.qmd#recipient-required)`r req_style` | | |        Other Contacts (multiple) | [Required](project_records/funding_tab_project.qmd#other-contacts-required)`r req_style`| | |        Marked Funds | [If Applicable](project_records/funding_tab_project.qmd#marked-funds-if-applicable)`r if_style` | | | Time Period | | | -|        Dates | [Required](project_records/funding_tab_project.qmd#dates-required)`r req_style`^\*^ | | +|        Dates | [Required](project_records/funding_tab_project.qmd#dates-required)`r req_style` | | | Description (multiple) | [Best Practice](project_records/funding_tab_project.qmd#description-best-practice)`r best_style` | | -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"} -^\*^Also required under the ScienceBase 30-day Policy
    ## Contacts @@ -155,6 +150,6 @@ Certain metadata fields are required for Individual or Organization contacts. | Online Resource | | [Required](contact_records/organization_contacts.qmd#create-a-new-contact)`r req_style` | | Physical Address | [Best Practice](contact_records/individual_contacts.qmd#create-a-new-contact)`r best_style` | [Best Practice](contact_records/organization_contacts.qmd#create-a-new-contact)`r best_style` | | Logo | | [Best Practice](contact_records/organization_contacts.qmd#create-a-new-contact)`r best_style` | -: {.striped .hover .bordered .sm .allborder} +: {.striped .hover .bordered .sm .allborder tbl-colwidths="[50, 25, 25]"}
    diff --git a/content/product_records/main_tab_product.qmd b/content/product_records/main_tab_product.qmd index df5251e..cfe213c 100644 --- a/content/product_records/main_tab_product.qmd +++ b/content/product_records/main_tab_product.qmd @@ -16,8 +16,8 @@ The **Main** tab allows for the creation and/or editing of primary metadata. | Metadata Field | Product Records | |:------------------------------|:-------------| | Basic Information | | -|        Title | [Required](#title)`r req_style`^\*^ | -|        Status | [Required](#status)`r req_style`^\*^ | +|        Title | [Required](#title)`r req_style` | +|        Status | [Required](#status)`r req_style` | | Default Locale | [Required](#default-locale-required)`r req_style` | | Resource Type | [Required](#resource-types)`r req_style` | | Points of Contact | | @@ -25,12 +25,12 @@ The **Main** tab allows for the creation and/or editing of primary metadata. |        Custodian | [Required](#point-of-contacts)`r req_style`| |        Administrator | | |        Administrative Region | [Required](#point-of-contacts)`r req_style`| -|        Principal Investigator | [If Applicable](#point-of-contacts)`r if_style`^\*^ | +|        Principal Investigator | [If Applicable](#point-of-contacts)`r if_style` | |        Co-Principal Investigator | [If Applicable](#point-of-contacts-if-applicable)`r if_style` | | Citation | | -|        Title | [Required](#title)`r req_style`^\*^| +|        Title | [Required](#title)`r req_style`| |        Dates (multiple) | [If Applicable](#dates-if-applicable)`r if_style` | -|        Responsible Parties (multiple) | [Required](#responsible-parties-required)`r req_style`^\*^ | +|        Responsible Parties (multiple) | [Required](#responsible-parties-required)`r req_style` | |        Online Resource | | |               Name | [If Applicable](#online-resource)`r if_style` | |               URL | [If Applicable](#online-resource)`r if_style` | @@ -39,10 +39,10 @@ The **Main** tab allows for the creation and/or editing of primary metadata. |               Identifier | [Required](#metadata-identifier-required)`r req_style` | |               Namespace | [Required](#metadata-namespace-required)`r req_style` | | Description | | -|        Abstract | [Required](#abstract)`r req_style`^\*^ | +|        Abstract | [Required](#abstract)`r req_style` | | Time Period | | |        Start Date | [If Applicable](#time-period)`r if_style` | -|        End Date | [Required](#time-period)`r req_style`^\*^ | +|        End Date | [Required](#time-period)`r req_style` | : {.striped .hover .bordered .sm .allborder}
    diff --git a/content/project_records/main_tab_project.qmd b/content/project_records/main_tab_project.qmd index 6e10f2c..0312f0b 100644 --- a/content/project_records/main_tab_project.qmd +++ b/content/project_records/main_tab_project.qmd @@ -30,8 +30,8 @@ The **Main** tab allows for the creation and/or editing of primary metadata. |        Principal Investigator | [If Applicable](#points-of-contact-required)`r if_style`^\*^ | |        Co-Principal Investigator | [If Applicable](#points-of-contact-required)`r if_style`| | Citation | | -|        Title | [Required](#title-required-1)`r req_style`^\*^ | -|        Dates (multiple) | [Required](#dates-required)`r req_style`^\*^ | +|        Title | [Required](#title-required-1)`r req_style` | +|        Dates (multiple) | [Required](#dates-required)`r req_style` | |        Responsible Parties (multiple) | [Required](#responsible-parties-required)`r req_style`^\*^ | |        Online Resource | | |               Name | [If Applicable](#online-resource-if-applicable)`r if_style`| @@ -41,10 +41,10 @@ The **Main** tab allows for the creation and/or editing of primary metadata. |               Identifier | [Required](#metadata-identifier-required)`r req_style` | |               Namespace | [Required](#metadata-namespace-required)`r req_style` | | Description | | -|        Abstract | [Required](#abstract)`r req_style`^\*^ | +|        Abstract | [Required](#abstract)`r req_style` | | Time Period | | -|        Start Date | [Required](#time-period)`r req_style`^\*^ | -|        End Date | [Required](#time-period)`r req_style`^\*^ | +|        Start Date | [Required](#time-period)`r req_style` | +|        End Date | [Required](#time-period)`r req_style` | : {.striped .hover .bordered .sm .allborder}
    diff --git a/content/roles_and_responsibilities.qmd b/content/roles_and_responsibilities.qmd index 8a43e95..22938c6 100644 --- a/content/roles_and_responsibilities.qmd +++ b/content/roles_and_responsibilities.qmd @@ -19,7 +19,7 @@ Definition​: Assistant Regional Directors for Science Applications - Sign memo stating a project intended for funding is not duplicative research or other science activity (Science Project) and therefore does not need to go through any additional steps in the [Non-Duplication - Policy](non_duplication_policy.qmd). + Policy](appendix/non_duplication_policy.qmd). - Sign ​CASC Consultation Certification memo​ stating the CASC consultation took place and identified not duplication of funding between SA and a CASC. For grants and cooperative agreements, this can be certified by diff --git a/content/science_catalog.qmd b/content/science_catalog.qmd index ce711a4..3e1d831 100644 --- a/content/science_catalog.qmd +++ b/content/science_catalog.qmd @@ -34,7 +34,7 @@ have been published to ScienceBase. | **Resource Type** | [Main Tab: Resource Type](project_records/main_tab_project.qmd#resource-types-required) | [Main Tab: Resource Type](product_records/main_tab_product.qmd#resource-types-required) | | **Title** | [Main Tab: Title](project_records/main_tab_project.qmd#title-required) | [Main Tab: Title](product_records/main_tab_product.qmd#title-required) | | **Source** | ScienceBase folder location^**1**^ | ScienceBase folder location^**1**^ | -| **Fiscal Years Funded** | [Funding Tab: Allocation: Time Period: Dates](project_records/funding_tab_project.qmd#dates-required) | [Associated Project](product_records/associated_tab_product.qmd)^**2**^ | +| **Fiscal Years Funded** | [Funding Tab: Funding Period: Time Period: Dates](project_records/funding_tab_project.qmd#dates-required) | [Associated Project](product_records/associated_tab_product.qmd)^**2**^ | | **Last Update Date** | [Main Tab: Citation: Dates](project_records/main_tab_project.qmd#dates-required) | [Main Tab: Citation: Dates](product_records/main_tab_product.qmd#dates-required) | | **Status** | [Main Tab: Status](project_records/main_tab_project.qmd#status-required) | [Main Tab: Status](product_records/main_tab_product.qmd#status-required) | | **Project Dates (multiple)** | [Main Tab: Citation: Dates](project_records/main_tab_project.qmd#dates-required) | [Main Tab: Citation: Dates](product_records/main_tab_product.qmd#dates-required) | diff --git a/content/workflow/metadata_editing_republishing.qmd b/content/workflow/metadata_editing_republishing.qmd index ead5386..e30a99b 100644 --- a/content/workflow/metadata_editing_republishing.qmd +++ b/content/workflow/metadata_editing_republishing.qmd @@ -100,8 +100,3 @@ publishing can alter records, like adding or changing a ScienceBase ID. The [SA Science Catalog](https://www.fws.gov/science/catalog/) updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks. - -### 13. Consult QA/QC resources. - -See the [QA/QC Fixes](../trouble_shooting/qa_qc_fixes.qmd) page for suggestions -about updating your data to check your metadata. diff --git a/content/workflow/metadata_from_scratch.qmd b/content/workflow/metadata_from_scratch.qmd index cae59cd..de1e8ff 100644 --- a/content/workflow/metadata_from_scratch.qmd +++ b/content/workflow/metadata_from_scratch.qmd @@ -117,7 +117,3 @@ The [SA Science Catalog](https://www.fws.gov/science/catalog/) updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks. -### 13. Consult QA/QC resources. - -See the [QA/QC Fixes](../trouble_shooting/qa_qc_fixes.qmd) page for suggestions -about updating your data to check your metadata. diff --git a/content/workflow/metadata_sciencebase_first.qmd b/content/workflow/metadata_sciencebase_first.qmd index 9012273..44363a4 100644 --- a/content/workflow/metadata_sciencebase_first.qmd +++ b/content/workflow/metadata_sciencebase_first.qmd @@ -97,7 +97,3 @@ The [SA Science Catalog](https://www.fws.gov/science/catalog/) updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks. -### 13. Consult QA/QC resources. - -See the [QA/QC Fixes](../trouble_shooting/qa_qc_fixes.qmd) page for suggestions -about updating your data to check your metadata. diff --git a/content/workflow/workflow_overview.qmd b/content/workflow/workflow_overview.qmd index 032892a..28ed0d6 100644 --- a/content/workflow/workflow_overview.qmd +++ b/content/workflow/workflow_overview.qmd @@ -127,7 +127,3 @@ The [SA Science Catalog](https://www.fws.gov/science/catalog/) updates overnight so you should review newly-published records the day after you publish to ScienceBase. This will be one of your best quality control checks. -### 13. Consult QA/QC resources. - -See the [QA/QC Fixes](../trouble_shooting/qa_qc_fixes.qmd) page for suggestions -about updating your data to check your metadata. diff --git a/index.qmd b/index.qmd index 7350bcd..431482a 100644 --- a/index.qmd +++ b/index.qmd @@ -72,7 +72,9 @@ This document will continue to be updated regularly and publishing using the [GitHub Repository](https://github.com/USFWS/Science_Applications_Metadata_Guidance). Please refresh this manual every time you open it to ensure you are viewing the most recent -version. **Last updated:** **`r todays_date`**. +version. + +Guidance was last updated: **`r todays_date`**. ## Providing Feedback @@ -82,6 +84,6 @@ this guidance, you can use this [online form](https://forms.office.com/g/xtkDZ3r If you’d like to give direct feedback through Github, please consider reporting an [issue](https://github.com/USFWS/sciapps_metadata_guidance/issues/new) or submitting edits through a -[pull request](https://github.com/USFWS/sciapps_metadata_guidance). However, +[pull request](https://github.com/USFWS/sciapps_metadata_guidance/pulls). However, in order to access these functions, you will be required to sign in or create an account with Github. \ No newline at end of file