The requirement in this case is for a metadata record to be composed in the Integrated Publishing Toolkit and output to a process that creates a RTF document from the published metadata EML file. The use cases described here support:

Requirements expressed by Vishwas for publication of a peer-reviewed data paper through the data publishing mechanism described by {Link to ZooKeys data paper document here} Vishwas Chavan.
ECAT requirements for use cases where a data publisher wishes to compose a metadata document via the IPT and host that document in the IPT.

1.1	In this example, a user (1.1) uses the web interface of the IPT to compose an EML metadata document that is based on the "IPT metadata profile", based on a subset of the complete EML schema. The IPT provides a web-based form for composing the metadata.

1.2	The submitted metadata content is stored within the IPT internal database.

1.3	The user publishes the metadata using the IPT publication workflow process. The IPT outputs a EML XML document based on the IPT EML profile.

1.4	A text processing script or style sheet transforms the IPT profile XML document to corresponding document formatted as Rich Text Format.

1.5	The user references this file and proceeds to the data paper submission process Use Case

Note: It remains unclear what initiates the process 1.4.

Use Case #2 EML Metadata composed external to the IPT

This use case supports the requirements for publication of a peer-reviewed data paper through the data publishing mechanism described by {Link to ZooKeys data paper document here} Vishwas Chavan. The requirement in this case is to

- support the creation of metadata documents via other means external to the IPT that include composing metadata offline and asynchronously. - supports the creation of metadata documents that are more detailed than are supported by the IPT metadata profile.

This use case supports some ECAT requirements where publishers of taxonomic checklists may compose and host metadata documents externally or according to different metadata standards.

2.1	A user composes a EML document (2.2) using a non-IPT metadata authoring tool such as Morpho.
2.2	Included in 2.1 above
2.3	The user uploads the externally-composed metadata document to the IPT via a file upload option. The metadata document is copied and stored on the local file system. It is not stored in the IPT database. To support this the IPT must either parse and store a minimal set of the metadata stored in the file (ex. title) or present a minimal form for the user to complete in association with the metadata file. This is to provide the means to reference the resource via title in the IPT display.
2.4	A text processing script or style sheet transforms the EML XML document to corresponding document formatted as Rich Text Format.
1.5	See 1.5 above.

Use Case #3 ISO Metadata composed external to the IPT

Same as Use Case #2 but supports the upload and transformation of ISO 19115 metadata documents.

3.1	A user composes a ISO metadata document (3.1) using a non-IPT metadata authoring tool.
3.2	A text processing script or style sheet transforms the ISO metadata document to corresponding document formatted as Rich Text Format. (1.5)

Use Case #4 Dublin Core Metadata composed external to the IPT

Same as Use Case #2 but supports the upload and transformation of Dublin Core metadata documents.

4.1	A user composes a Dublin Core metadata document (3.1) using a non-IPT metadata authoring tool.
4.2	A text processing script or style sheet transforms the Dublin Core metadata document to corresponding document formatted as Rich Text Format. (1.5)

Use Case #5 FGDC Metadata composed external to the IPT

Same as Use Case #2 but supports the upload and transformation of FGDC metadata documents.

5.1	A user composes a FGDC metadata document (3.1) using a non-IPT metadata authoring tool.
5.2	A text processing script or style sheet transforms the FGDC metadata document to corresponding document formatted as Rich Text Format. (1.5)

Use Case #6 NCD Metadata composed external to the IPT

Same as Use Case #2 but supports the upload and transformation of NCD metadata documents.

6.1	A user composes a NCD metadata document (3.1) using a non-IPT metadata authoring tool.
6.2	A text processing script or style sheet transforms the NCD metadata document to corresponding document formatted as Rich Text Format. (1.5)

► Sign in to add a comment