You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Purpose,To clarify to the user if the resource is public (any user can access) or restricted (a user will need to log in to some kind of authentication protocol) and if the application should provide a web service preview and/or a download function
6
+
Multivalued,False
7
+
Purpose,To clarify to the user if the resource is public (any user can access) or restricted (a user will need to log in to some kind of authentication protocol) and if the application should provide a web service preview and/or a download function.
8
8
Entry Guidelines,Only one of two values are allowed: Public or Restricted.
9
9
Commentary,"This field can be set to ""Public"", which allows users to view and download an item, or ""Restricted"", which requires a user to log in to an authentication service."
Purpose,To provide the user with the another title if needed
6
+
Multivalued,True
7
+
Purpose,To provide the user with the another title if needed.
8
8
Entry Guidelines,This could be for a secondary or original title or subtitle.
9
9
Commentary,"For discoverability, improving titles for data is encouraged. This field could be a place to keep the original title. It could also be useful for scanned maps. Some have long titles that include MARC subtitle fields, such as 245$b. Whether or not this field should appear in your GeoBlacklight item view pages can be customized in the application."
Purpose,To credit the person/organization that collected or authored the resource
8
-
Entry Guidelines,The suggested controlled vocabulary is the Library of Congress Name Authority File.
9
-
Commentary,"This field is best reserved for instances in which an individual person has collected, produced, or generated analyses of data (as opposed to an agency releasing a data product or resource). It can be a person or an organization."
10
-
Controlled Vocabulary,no
11
-
Example value,"[""Geological Survey (U.S.)""]"
6
+
Multivalued,True
7
+
Purpose,To credit the person/organization that collected or authored the resource.
8
+
Entry Guidelines,The suggested controlled vocabulary is the [Library of Congress Name Authority File](https://id.loc.gov/authorities/names.html).
9
+
Commentary,"The distinction between Creator and [Publisher](../ogm-aardvark/#publisher) is often vague. This field is best reserved for instances in which an individual person has collected, produced, or generated analyses of data (as opposed to an agency releasing a data product or resource). It can be a person or an organization."
Purpose,"To provide the user with the date when an item was published, and for administrators to determine the age of the resource"
6
+
Multivalued,False
7
+
Purpose,"To provide the user with the date when an item was published, and to allow administrators to determine the age of the resource."
8
8
Entry Guidelines,"A single year is the preferred format. For more precise dates, use the ISO format without the time value: YYYY-MM-DD or YYYY-MM."
9
-
Commentary,"Although the field is optional, it is often useful when a clear Temporal Coverage value is not present. For example, one may want to preserve a dataset with an uncertain lineage, but there is an indicator on a data portal on the date of last update. In most cases, the 4-digit year is sufficient."
10
-
Controlled Vocabulary,no
11
-
Example value,"""1999"""
9
+
Commentary,"Although the field is optional, it is often useful when a clear [Temporal Coverage](../ogm-aardvark/#temporal-coverage) value is not present. For example, one may want to preserve a dataset with an uncertain lineage, but there is an indicator on a data portal on the date of last update. In most cases, the 4-digit year is sufficient."
Purpose,To power other time widgets that use a date range
8
-
Entry Guidelines,"Enter a start date and end date in the Solr date range field convention. In JSON, the value should be formatted as a string that includes the brackets, rather than as an array or list containing a string. Incorrect: [""YYYY TO YYYY""] - Correct: ""[YYYY TO YYYY]"""
6
+
Multivalued,True
7
+
Purpose,To power other time widgets that use a date range.
8
+
Entry Guidelines,"Enter a start date and end date in the Solr date range field convention. In JSON, the value should be formatted as a string that includes the brackets, rather than as an array or list containing a string. Incorrect: [""YYYY TO YYYY""]. Correct: ""[YYYY TO YYYY]""."
9
9
Commentary,"This field is not yet supported by GeoBlacklight, but the application can be customized to use it."
Purpose,To provide the user with a summary of the resource
8
-
Entry Guidelines,"At minimum, this is a reiteration of the title in sentence format. Other relevant information, such as data creation methods, data sources, and special licenses, may also be included. Description is a plain text field by default."
9
-
Commentary,"This field is the second-most prominent value (after Title) that users see when search or browsing for items. Although not required, it is strongly recommended. If the description is minimal or lacking, it can be improved by concatenating available metadata fields, such as title, date, format, and place. This is a plain text field, so html code is not supported here unless the application is customized."
10
-
Controlled Vocabulary,no
11
-
Example value,"""This polygon shapefile represents boundaries of election districts in New York City. It was harvested from the NYC Open Data Portal."""
6
+
Multivalued,True
7
+
Purpose,To provide the user with a summary of the resource.
8
+
Entry Guidelines,"At a minimum, this is a reiteration of the title in sentence format. Other relevant information, such as data creation methods, data sources, and special licenses, may also be included."
9
+
Commentary,"This field is the second-most prominent value (after [Title](../ogm-aardvark/#title)) that users see when search or browsing for items. Although not required, it is strongly recommended. If the description is minimal or lacking, it can be improved by concatenating available metadata fields, such as title, date, format, and place. This is a plain text field by default, but it can include clickable links if the GeoBlacklight software is customized; see the [GeoBlacklight documentation](https://geoblacklight.org/docs/customization/rendering_html_from_description/) on how to render HTML from a text field."
10
+
Controlled Vocabulary,No
11
+
Example Value,"""This polygon shapefile represents boundaries of election districts in New York City. It was harvested from the NYC Open Data Portal."""
Purpose,"To highlight additional information about a resource, such as warnings or tips for using the data."
8
-
Entry Guidelines,"Prefix the string with ""Warning:"", ""Info:"", or ""Tip:"" to specify the type of note. Future versions of GeoBlacklight will use such prefixes to control the style of the displayed note. Styles and additional prefixes (for example, in other languages) can be added in the GeoBlacklight config."
9
-
Commentary,"This field is currently only supported by customizations to the GeoBlacklight application. On the item page, text in this field will be prominently displayed in a shaded box just after the title."
10
-
Controlled Vocabulary,no
11
-
Example value,"[""Warning: This text (starting with 'This text') will be displayed in a red box"",""Info: This text (starting with 'This text') will be displayed in a blue box"",""Tip: This text (starting with 'This text') will be displayed in a green box"",""This is text without a tag and it will be assigned the default 'note' style""]"
8
+
Entry Guidelines,"Prefix the string with ""Danger:"", ""Info:"", ""Tip:"", or ""Warning:"" to specify the type of note."
9
+
Commentary,"Starting in GeoBlacklight version 4.1, text in this field is prominently displayed in a shaded box just after the title, with the prefixes controlling the style of the displayed note. Styles and additional prefixes (for example, in other languages) can be added by customizing the GeoBlacklight software; see the [v4.1.0 release notes](https://github.com/geoblacklight/geoblacklight/releases/tag/v4.1.0)."
10
+
Controlled Vocabulary,No
11
+
Example Value,"[""Danger: This text will be displayed in a red box"",""Info: This text will be displayed in a blue box"",""Tip: This text will be displayed in a green box"",""Warning: This text will be displayed in a yellow box"",""This is text without a tag and it will be assigned the default 'note' style""]"
0 commit comments