Access constraints are applied to assure the protection of privacy or intellectual property and any special restrictions or limitations on obtaining the resource.
-
-
Use Constraints ([If applicable])
+
+
Use Constraints (If applicable)
How the product should be used.
@@ -755,9 +755,10 @@
Sensitive/Protec
Restricted Access
-
-
-
Security Constraints
+
+
Security Constraints
+
+
Classification (If applicable)
A place to describe constraints or restrictions pertaining to security of the resource. Choose security classification from the drop-down menu. For products without restrictions, best practice is to select unclassified from the menu.
Adding keywords to your metadata record allows for the record to be found later through a search engine, keywords are the way to tag your projects or products. The mdEditor is designed using thesauruses that contain pre-determined keywords. These thesauruses create a ‘controlled vocabulary’ so that all SA staff adding metadata can adhere to the same standards, and future search results can return clear results of projects and products.
Keywords Tab
-
-
{.striped .hover .bordered .sm .allborder}
-
+
Metadata Field
@@ -695,6 +693,7 @@
Keywords Tab
+
To add Keywords to your Product Record
@@ -828,8 +827,8 @@
SA Priority Area
-
-
Science Topic (Required)
+
+
SA Science Topic (Required)
Choose all that apply. The list of options includes the following:
@@ -1038,8 +1037,8 @@
-
Global Change Master Directory (GCMD) ([Best Practice])
+
+
Global Change Master Directory (GCMD) ([Best Practice])
GCMD stands for Global Change Master Directory and these keywords are maintained by NASA. Look for useful keywords in the GCMD Science Keywords. There are GCMD Platforms and Instruments Keywords but they are unlikely to apply to SA projects.
The Main tab allows for the creation and/or editing of primary metadata.
-
-
{.striped .hover .bordered .sm .allborder}
+
Metadata Field
@@ -784,6 +783,7 @@
Main Tab
+
Basic Information
@@ -822,9 +822,10 @@
Resource Types
-
-
Point of Contacts (Required)
+
+
Points of Contact (Required)
Adding 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.
+
Add additional Points of Contact as listed in the table below.
@@ -1062,12 +1063,9 @@
Supplemental Info
Time Period
-
-
Dates (If available)
-
Time Period refers to project start and end date, or the date that the product was applicable. For example, the time when a map is valid, date of publication, date of presentation, or dates when the data was collected.
-
-
Required: For each product, add a start date and end date.
-
+
+
Start Date and End Date (Required)
+
Time Period refers to when date the product was applicable, For example, the time when a map is valid, date of publication, date of presentation, or dates when the data was collected. For each product, enter a Start Date and End Date.
The Metadata tab describes your project’s metadata, including a description that outlines the process of metadata creation, contributors to the creation of the metadata, and metadata repositories.
In some cases, funds are marked for specific activities and include reporting requirements that accompany the funding allocations. For example, EPA allocates Great Lakes Restoration Initiative (GLRI) funds on behalf of Congress to FWS, among others. FWS then distributes the funds across programs for use. The Gulf Coast Restore funds are a similar case. This funding flow can be tracked and aggregated with the Funding Other Contacts. Add the Name of the funding source as an organization contact and add the funding source as the “funder” in Funding Other Contacts.
@@ -804,26 +803,7 @@
Marked Fundin
Example of organizational fund contact entry
-
-
-
-Example of organizational fund entry in Funding metadata entry
-
-
-
-
-
Description (Best Practice)
-
In order to better integrate budgeting records and align with activity tracking priorities, add the FWS Sub-Activity, Funding Codes, and Agreement Type to the Description.
-
For example, the text entry may look like this: FWS sub-activity 1420, fundcode 190, contract. If funds are provided from multiple sub-activities, please add this in the description (i.e. FWS sub-activity 1430, fundcode 170, $30,000: sub-activity 1420, fundcode 170, $10,000). At some point in the future, mdEditor may include additional fields for these values.
-
-
-
-Example budgeting information in Allocation Description
-
-
-
-
-
Matching and In-kind Funds (If applicable)
+
### Matching and In-kind Funds (If applicable)
Project funds or in-kind support that were supplied by a partner (i.e., not specifically allocated to SA) should be included as an allocation as described above, but with the matching fund box checked. Each matching fund provider needs to be included as a separate allocation.
@@ -852,6 +832,17 @@
Dates (
+
+
+
Description (Best Practice)
+
In order to better integrate budgeting records and align with activity tracking priorities, add the FWS Sub-Activity, Funding Codes, and Agreement Type to the Description.
+
For example, the text entry may look like this: FWS sub-activity 1420, fundcode 190, contract. If funds are provided from multiple sub-activities, please add this in the description (i.e. FWS sub-activity 1430, fundcode 170, $30,000: sub-activity 1420, fundcode 170, $10,000). At some point in the future, mdEditor may include additional fields for these values.
+
+
+
+Example budgeting information in Allocation Description
+
+
Example of multiple allocations across several fiscal years for a single project record.
Choose all that apply. The list of options includes the following:
@@ -908,8 +908,8 @@
Science Topic (
-
-
Conservation Action Open Standard (Requied, if applicable**)
+
+
Conservation Action Open Standard (If applicable**)
The Open Standards for the Practice of Conservation is a globally utilized nomenclature for conservation. Including these keywords helps to align the work of USFWS Science Applications with global conservation efforts and to utilize the shared resources of the Conservation Standards Network. The open standards keywords for conservation actions are as listed:
@@ -1037,8 +1037,8 @@
-
GCMD (Best Practice)
+
+
Global Change Master Directory (GCMD) (Best Practice)
GCMD stands for Global Change Master Directory and these keywords are maintained by NASA. Look for useful keywords in the GCMD Science Keywords. There are GCMD Platforms and Instruments Keywords but they are unlikely to apply to SA projects.
Resource Types For projects, the Resource Type should be automatically filled in with the resource type you selected when you created your record. This should be “project” for all SA projects. Name is optional - you can leave this blank or enter a shorten project name.
-
-
Points of Contacts (Required)
-
Adding a Point of Contact gives users information on who to contact should they have a question regarding your project or product.
-
-
-
-
-
-
-Note
-
-
-
-
To add contacts to a metadata record, you must first create/upload the contacts into mdEditor. See the Contact Records Section for more information.
-
-
+
+
Points of Contact (Required)
+
Adding 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.
+
Add additional Points of Contact as listed in the table below.
@@ -1061,8 +1049,8 @@
Supplemental Info
Time Period
-
-
Dates (Required)
+
+
Start Date and End Date (Required)
For each project, add a Start Date and End Date. If the project spanned a single fiscal year, you can use the “Pick a Fiscal Year” drop-down to autofill the date fields.
The Taxonomy tab allows taxonomic information the species associated with the project or product. Taxonomy is required for projects and strongly recommended for products (if applicable).
