Portal Metadata Explained

Metadata\n\nInformation on Creating Metadata for your Spatial Collaboration and Hosting Portal products.\n\nData Publishers are responsible for providing and maintaining appropriate metadata to ensure\nthat users have all\nthe information required\nto understand the dataset and assess whether\nit is fit for their requirements. This must\ninclude up to date contact\ndetails of the Data Custodian or Data Provider.\n\nProviding standards-based metadata with your item helps people learn about the item and decide which item best meets their needs. In DCS Spatial\nServices’ Spatial Collaboration and Hosting Portals,\nthe metadata is saved with the item it describes.\n\nMetadata provides\nthe means for discovering spatial\ninformation by identifying ‘what,’ ‘where,’ ‘who,’\n‘when,’ and ‘how’ the data behind\nthe information is constructed. Metadata\nis the means to disclose\nwhat the spatial\ndata describes, as well as how it should and can be used, along with any\nlimitations and restrictions.\n\nTo assist\nin maintaining the standard of content published\nto the portal, Spatial Services\nhave implemented the auto-injection of a metadata\ntable into all new content\ncreated or exiting\ncontent that has had a change to the\nshare status. This new template will have an enforcement on several fields as a\nminimum requirement to be completed before a new service can be shared. This is\nto ensure that the services published in the portal are supported with the\nminimum amount of information to be published with all new content.\n\nChanges to Metadata collection in the Hosting\nand Collaboration Portal:\n-\n\n       •        \nAll new content\ncreated will have the approved\nmetadata table auto-injected into                     the item\n\n       •        \nFields that have an enforcement are shaded green\n\n       •        \nThe publisher is required to complete all the required\nfields in the table shown\nin                      green\n\n       •        \nThe green fields\nare either open text or have pre-populated options for selection\n\n  •        \nWhere\npre-populated selections are available, please remove all the content,                    leaving\nyour identified option. Do not leave any spaces or commas, etc\n\n       •        Once these minimum\nrequirements are met, the service\ncan be shared\n\nAll Portal\ncontent fields should\nbe completed, including tags, etc., to keep the content discoverable and useful to the end user. The Item information\nscore should be green and sit at 100%.\n\nAuto Inject Table ExplainedContent TitleThe name of the Dataset, as assigned by the data provider or Data Custodian.Eg Polygon dataset representing Administrative Boundaries. Try and make you title descriptive or representative about the about data or product you are publishing. A Web Map or Feature service of Sydney Train Lines could be Sydney Train Lines instead of SYD798.gdb the default name of the data set being published.Enforced FieldOpen TextContent TypeThe type of dataset or content i.e. Hosted Feature Layer, Web Map, Web ApplicationEg.Hosted feature layer  Enforced FieldPopulated options for selectionHosted Feature Layer, Web Map, Web Application, Aerial Imagery, Basemap, Table, Scene Layer/Scene Layer Package, Datastore, 2D Data, 3D Data, OtherDescriptionShort explanation of the contents of the dataset.Eg. Polygon dataset representing Administrative Boundaries can be the same as the page field Add a brief summary about the item.Enforced FieldOpen TextInitial Publication DateDate in which the item was first published into PortalEg.06/10/2022Enforced FieldDate formatDD/MM/YYYYData CurrencyDate of the most recent update of the dataset.