The tool shall include products in the manifests based upon the following criteria (see Details below for more detailed information):
Bundle (B) specified as input to the tool and any associated readme (R)
Primary Collections (C1, C2, C3) associated with that Bundle (B)
Primary products associated each of those Collections (C1, C2, C3)
Assumptions
Products include both the label (.xml) and the files referenced from it.
Any file_name referenced in a label can be assumed it is in the same directory as the parent product.
Any collections referenced by LID will only include latest version of associated collections in SIP and AIPs (flag to disable this and include all collections for backwards compatibility).
Details
1. Bundle (B) specified as input to the tool and any associated readme (R)
Requirement
The tool shall include products in the manifests based upon the following criteria (see Details below for more detailed information):
Assumptions
file_name
referenced in a label can be assumed it is in the same directory as the parent product.Details
1. Bundle (B) specified as input to the tool and any associated readme (R)
//File_Area_Text/File/file_name
) (See Assumption 2 above for where to look)2. Primary Collections (C1, C2, C3) associated with that Bundle (B)
To identify the primary collections of a bundle get the LIDs/LIDVIDs per:
//Bundle_Member_Entry/lidvid_reference/
+//Bundle_Member_Entry/member_status/value() == Primary
//Bundle_Member_Entry/lid_reference/
+//Bundle_Member_Entry/member_status/value() == Primary
(see Assumption 3 above)To find those products, assume any collections referenced by the bundle will be in the same directory or in any sub-directory of the input bundle.
3. Primary products associated with each of those Collections (C1, C2, C3)
From collection labels C1, C2, C3, here is how we can get the product LID/LIDVIDs:
//File_Area_Inventory/File/file_name/
and//Inventory/field_delimiter/
to prepare to parse the inventory.P
, not anS
(secondary))