Filling Out the Bundle Member Entry Class

From The SBN Wiki
Revision as of 21:20, 3 August 2020 by Raugh (talk | contribs) (Update for IM
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The <Bundle_Member_Entry> class creates an association between the Bundle and one of its member Collections.

For additional explanation, see the PDS4 Standard Reference, or contact your PDS node consultant.

Following are the attributes you'll find in <Bundle_Member_Entry>, in label order.

Note that in the PDS4 master schema, all classes have capitalized names; attributes never do.

<lid_reference> or <lidvid_reference>


This is either a logical ID (LID) reference or a LID reference with an additional version ID (VID) of a Collection product. If <lid_reference> is used, the value must match the <logical_identifier> value of a Collection product in the registry (this will be checked when the product is officially registered). Similarly, when a <lidvid_reference> is used, the value has the format logical_identifier::version_identifier, and there must be a Collection product with the given <logical_identifier> and <version_identifier> values.

Note: If you are planning to request a DOI for this bundle, then you must identify all member collections by version as well as LID (i.e., by "LIDVID").



Every Collection is a primary member of exactly one Bundle - the Bundle on which its logical_identifier is based. A Collection may be a secondary member of any number of additional bundles. This attribute must have the value Primary if the collection is a primary member of this bundle; or Secondary otherwise.



This attribute indicates what sort of information the Collection contributes to the Bundle. It supports certain registry searches, so be as specific as possible. The value must be one of the values listed in the Standard Values Quick Reference.