Difference between revisions of "Filling Out the Collection Class"
(Creation) |
(: Replace "Questions" links) |
||
| Line 9: | Line 9: | ||
''REQUIRED'' | ''REQUIRED'' | ||
| − | This attribute, which may only occur once, must have one of these standard values listed on the [[ | + | This attribute, which may only occur once, must have one of these standard values listed on the [[Standard Values Quick Reference]] page. |
Products should be collected according to their product type - documents in one collection, observational data in another, browse products in a third, and so on. If you have a collection that you feel strongly should contain multiple product types, talk to your PDS node consultant ''first''. | Products should be collected according to their product type - documents in one collection, observational data in another, browse products in a third, and so on. If you have a collection that you feel strongly should contain multiple product types, talk to your PDS node consultant ''first''. | ||
Revision as of 16:43, 24 January 2013
The <Collection> clas contains a single attribute to define the type of the collection, based on the primary content of the collection.
For additional explanation, see the PDS4 Standards Reference, or context your PDS node consultant.
Note that in the PDS4 master schema, all classes have capitalized names; attributes never do.
<collection_type>
REQUIRED
This attribute, which may only occur once, must have one of these standard values listed on the Standard Values Quick Reference page.
Products should be collected according to their product type - documents in one collection, observational data in another, browse products in a third, and so on. If you have a collection that you feel strongly should contain multiple product types, talk to your PDS node consultant first.
