InPort XML Version Changelog
Version 1.6November 24, 2020 Automatic NOAA Contact InsertionContacts referenced in InPort XML files (such as in Support Roles) -- which have a NOAA email address listed in <contact-email> (i.e. ending in "@noaa.gov") -- are now automatically added to InPort if they do not already exist. Note that in this scenario, the <contact-name> must also be present for the Contact to be automatically added. This feature is provided as a convenience for users, but we continue to recommend adding Contacts to InPort prior to loading, as the preferred approach. Version 1.5 Additional NoteSeptember 22, 2020 Contact Name Format RecommendationPreviously the recommended format for <contact-name> was [First Name] [Middle Name/Initials] [Last Name]. We are now recommending the format: [Last Name], [First Name] [Middle Name/Initials] Note that the actual functionality of the XML Loader has not been changed -- both formats have been and will continue to be supported. However, in practice, we have found that the use of the comma provides additional, helpful information for processing full person names, where the division between first, last and middle name can be ambiguous. Since XML Loader functionality has not been modified, we do not consider this recommendation change to be a version change. All XML Loader documentation and samples, however, now reflect this new recommendation. Version 1.5June 4, 2019 Publications and Publication InformationA new Catalog Item Type, Publication, has been added to InPort. In addition, a new section, Publication Information, has also been added. Please see the Publication Information documentation for more information. Date Field ConsolidationCertain date fields which were previously Catalog Item-type specific have now been consolidated into new fields in the Item Identification section, which apply across all Catalog Item Types. Deprecated Fields:
New Consolidated Fields:
The new fields also accept "Unknown" as a value, when it is desired to document the relevant date as being unknown. Version 1.41February 28, 2019 Reference SystemsA new subsection, Reference Systems, under the Spatial Information section, has been added. This subsection provides a way of documenting Spatial Reference System information used for a Data Set. Please see the Reference Systems documentation for more information. Coordinate Reference System URLThe field, Coordinate Reference System URL (<coordinate-reference-system-url>) under Vertical Extents has been removed from InPort and is no longer supported. It has been replaced by the <coordinate-reference-system> node, with a child node <epsg-code> which specifies the Coordinate Reference System EPSG Code as an identifier. Linking Share LevelThe Linking Share Level field (under the Catalog Details section) is no longer supported. Version 1.40November 15, 2018 Support RolesSupport Roles now refer to Contacts, rather than Persons or Organizations. Consequently, the fields <person-email> and <organization> have been deprecated. Instead, a Contact (which can be a Person, Organization or Position) should now be identified with a <contact-email> or <contact-name>. In addition, the <contact-type> must be specified. Support Roles using the deprecated <person-email> or <organization> fields will continue to be processed for a temporary transitional period, but will match against InPort Contacts and not InPort Persons or Organizations. See the full InPort XML Loader documentation on Support Roles for more information. Distributors (in Distribution Information)Since Support Roles now refer to Contacts rather than Persons or Organizations, references to Distributors in the Distribution Information section should also refer to these Contacts. Consequently, the fields <person-email> and <organization> have been deprecated. Instead, the Contact specified as the Distributor should now be identified with a <contact-email> or <contact-name>. In addition, the <contact-type> must be specified. Distributors using the deprecated <person-email> or <organization> fields will continue to be processed for a temporary transitional period. Process Contacts (in Lineage Process Steps)Process Contacts now refer to Contacts, rather than Persons or Organizations. Consequently, the fields <process-contact-type>, <process-contact>, <process-contact-email> and <process-contact-phone> have been deprecated. Instead, a Contact (which can be a Person, Organization or Position) should now be identified with a <contact-email> or <contact-name>. In addition, the <contact-type> must be specified. Support Roles using the deprecated <person-email> or <organization> fields will continue to be processed for a temporary transitional period, but will match against InPort Contacts and not InPort Persons or Organizations. Instead, <process-contact> has been converted into a wrapping node for a reference to a Contact (which can be a Person, Organization or Position). The Contact can be identified with a <contact-email> or <contact-name>. In addition, the <contact-type> must be specified. Process Contacts using the deprecated <process-contact> field will continue to be processed for a temporary transitional period, but will match against InPort Contacts and not InPort Persons or Organizations. In addition, Non-InPort Persons and Organization specified with the <process-contact>, <process-contact-email>, or <process-contact-phone> fields are no longer supported and will be skipped during loading. See the full InPort XML Loader documentation on Lineage Process Steps for more information. Originators/Publishers (in Lineage Sources)Previously, the Originator/Publisher for a Source was specified with <originator-publisher-type> and <originator-publisher>. These fields are now deprecated and replaced by 3 new fields: <contact-role-type>, <contact-type> and <contact-name>. Note that unlike other sections, the <contact-name> field for Lineage Source is a standalone free text field, and not a reference to an InPort Contact. Consequently, it does not need to refer to a pre-existing InPort Contact. Sources using the deprecated <originator-publisher-type> and <originator-publisher> fields will continue to be processed for a temporary transitional period. See the full InPort XML Loader documentation on Lineage Sources for more information. FGDC Content TypeThe field, FGDC Content Type (from the Distribution Information section) has been deprecated and is no longer supported in the XML loader. Source Media TypeThe field, Source Media Type (from the Data Set Information section) has been deprecated and is no longer supported in the XML loader. Linking Share LevelThe field, Linking Share Level (in the Catalog Details section) has been deprecated, and is no longer supported in the XML loader. This field has been used to restrict what Catalog Items can be linked as Related Items. The field will be completely removed in a future release, after which any Catalog Items can be related to each other without restriction. Version 1.31May 24, 2018 Data Set Creation Date, Data Set Revision DateTwo new fields, Data Set Creation Date and Data Set Revision Date, have been added to the Data Set Information section. These are optional fields which refer to the creation date and revision date of the Data Set, respectively. Please see the Data Set Information documentation for more information. InPort XML Date/Time Format ChangesInPort XML now uses ISO 8601 extended format to represent date and time for better readability. However, the Loader will continue to accept both extended and basic format. Version 1.30January 23, 2018 A new section, Acquisition Information, has been added. This section provides a more detailed and reusable method for documenting Instruments, Platforms, and Physical Collection / Fishing Gear. It replaces the respective fields under the Data Set Information section, which are now deprecated. Please see the Acquisition Information documentation for more information. A number of additional fields have been added to various sections. Please consult the documentation links below for more information.
Version 1.22October 19, 2017 Source ContributionA new field, Lineage Source Contribution, has been added to the Lineage section. This field is an optional brief statement under a Lineage Source which identifies the information contributed by the source to the data set. Please see the Lineage documentation for more information. Version 1.21August 8, 2017 Currentness ReferencePrevious versions of InPort XML incorrectly used <currentness> as the XML name for the Currentness Reference field (in the Extents section). As of this version, it has been corrected to be <currentness-reference>. The old name <currentness> will continue to be supported for a temporary period, however it is strongly recommended to update to the corrected node name at the earliest convenience. Please see the Extents documentation for the updated documentation and examples. Version 1.20July 6, 2017 Spatial Information (Phase One)A new section, Spatial Information, has been added. This represents the first of two phases for supporting the ability to document spatial information-related metadata in InPort. Please see the Spatial Information documentation for detailed information on fields added in this release. Maintenance NoteA new field, Maintenance Note, has been added to the Data Set Information section. This field contains information regarding specific requirements for maintaining the resource. Please see the Data Set Information documentation for more information. CC ID
The previous version of the InPort XML Loader documentation incorrectly listed the CC ID
option as
a child node of the section or element it belonged to, rather than as an attribute of the
containing
element. The documentation has been corrected to fix this error, however the XML Loader
functionality
has not changed, and retains the original correct processing of Version 1.11April 4, 2017 Geographic AreasEach geographic area must contain either geographic bounds, or a description, or both. "Blank" geographic areas are not allowed. On an update, if the geographic bounds or description are removed, which results in a blank geographic area, the blank area will also be removed from the list of extents. Version 1.10March 14, 2017 Keywords
Keyword thesauri can no longer have the value "None". Keywords with no thesauri should not
include
the Distribution Information (formerly "Downloads")The Downloads (<downloads>) section has been renamed to Distribution Information (<distribution-information>). Each Download (<download>) is now referred to as a Distribution (<distribution>). In addition, three new fields have been added, which are also supported in the InPort XML Loader:
|
