Produce representations (metadata records) for four (4) items from your collection.
Records should follow rules/guidelines in your application profile/schema.
Records should be encoded in machine readable format.
For your projects, this means = records should be in a well-formed, but not necessarily valid, XML document.
For the difference between well-formedness and validity, see XML tutorial
Oxygen XML editor checks for well-formedness if you have not associated your XML document with a schema. Problems with well-formedness are indicated by red marks just to the right of the scrollbar. Click on the mark to be transported to the problem location and see an error description at the bottom of the window.
If you have created an XML schema for your project, your records should validate against that schema.
hint: Oxygen XML editor will reverse-engineer an XML schema document for any well-formed XML document.
With XML document open, do: Document >> XML Document >> Convert to…
This means: you can easily create a schema for the final incarnation of your project after creating your metadata records.
Elements whose values are constrained to an existing controlled vocabulary should be populated with terms from that vocabulary.
Elements whose values are defined as being controlled, but lacking the necessary controlled vocabulary, should be included but filled in with a placeholder: <name>Need controlled term</name>
The rest of the components for your project are devoted to developing subject languages