The Export successful window opens.Any Salesforce IDE (integrated development environment) can help you do this and offers a graphical interface to reduce the amount of package.xml manipulation you have to do to use the Metadata API. If you want to combine fields that contain multiple terms, select Combine fields that contain multiple terms.If you want to repeat fields that contain multiple terms, select Repeat fields that contain multiple terms.Determine how you want controlled vocabulary terms handled in the export.If you want to combine fields that use identical XML tags, select Combine fields that use identical XML tags.If you want to repeat fields that use identical XML tags, select Repeat fields that use identical XML tags.Determine how you want repeating fields handled in the export.Type XML tag names for the fields you wish to export.Select XML, and then choose Custom XML.Click the Collections tab and then click Export.Or access CONTENTdm Administration by navigating with your browser to: /cgi-bin/admin/start.exe Open CONTENTdm Administration by clicking CONTENTdm Administration from the Administration menu within the Project Client.Optionally, you can export page-level metadata for items that are part of compound objects, however in the export those items will not be organized within the context of the compound object structure. If you do not wish to export a field, leave the XML tag name blank.Ĭompound object structure cannot be exported using this format. The tags must be in the format specified by the third-party software that you are exporting to. When using the custom XML option, you enter the XML tags for the fields you are exporting. When exporting fields with controlled vocabulary, it allows you to repeat or combine fields that contain multiple controlled vocabulary fields. It also allows you to repeat fields that use identical XML tags or combine fields that use identical XML tags. For PDF compound objects and EAD files, the path to the complete print version of the file is provided instead of the path to the compound object.,Ĭustom XML allows you to determine the XML tags used for each field name. Note: CONTENTdm file path provides the full locations (URLs) for items. Used for harvesting CONTENTdm sites and can be used in OAI harvesting export applications Only fields mapped to Simple or Qualified Dublin Core Selected fields you specify custom tag namesĪfter registration map your fields to MARC and define a schedule for harvesting data into WorldCat Produces the SGML file that can be used with the DTD file to load a custom OCLC SiteSearch database Produces the SGML and DTD files that can be used to load a defined Dublin Core database Optionally can include page-level metadata for pages of compound objects (no structural information is included in this export so compound object pages are exported as individual items) Selected fields you specify XML tag names Option: Repeated field options for fields that contain multiple controlled vocabulary terms and fields that use identical XML tags Yes (full text field only or all page-level metadata)Ī simple XML schema that allows for user-specified XML names If fields are unmapped, they are tagged as unmapped This standard file format is used with spreadsheets and databases.Īn XML schema that exports according to the Dublin Core standardįields mapped to Qualified Dublin Core have XML tags names based on Dublin Core Text file containing metadata fields delimited by tab characters. Is page-level metadata in compound objects exported? ModeĮxported administrative/other metadata fields For more information, see the Help topic for each mode. The following table provides a quick reference to help you compare what is exported for each mode.
0 Comments
Leave a Reply. |