Archivists Toolkit: Description Functional Area

Transcription

1 : Description Functional Area Outline D1: Overview D2: Resources D2.1: D2.2: D2.3: D2.4: D2.5: D2.6: D2.7: Description Business Rules Required and Optional Tasks Sequences User intentions / Application response sequences Inputs Data flow diagram Screen sequences D3: Surrogates D3.1: D3.2: D3.3-11: D3.12: D3.13: D3.14: D3.15: Description Business Rules Required and Optional Tasks Sequences User intentions / Application response sequences Inputs Data flow diagram Screen sequences D4: Reports

2 D1: Description Functional Area: Overview Supporting the description of archival resources is the central function of the Toolkit. The description functional area allows the archivist to capture information about the physical and intellectual content of an archival resource, as well as contextual information about collection creators and topics. This information can then be output in various formats and used by researchers as a means of access to the materials. The inception of the Toolkit project was primarily driven by the need to create a number of different access tools that draw upon the same descriptive information, and the desire to do so using a single system that, ideally, allows the archivist to enter data once and output multiple formats. The description module will interact with all of the other modules in the Toolkit. Descriptions may inherit data from accession records, and may link to location, name, and subject records. The Toolkit will support description of archival resources in a variety of material formats, whether those resources exist as collections/fonds/record groups or as independent items. Collections/fonds/record groups may be represented by linked records that together form a multi-level description for the materials. The Toolkit will also support the description of surrogates, which are reproductions, in analog or digital data formats, of archival resources and stored and available apart from the archival resource. The diagram below is a high-level depiction of the various description record types that will exist in the AT, in support of multi-level description of archival resources and surrogates. The diagram also displays the hierarchical and linking relationships that can exist among the various description record types. There will be two different description record models in the Toolkit, one for archival resources and another for surrogates. These are discussed more thoroughly in sections D2 and D3. Description Functional Area: Overview Page:1

3 Figure 1. Record types and relationships of archival resources and their surrogates. The Toolkit s description module is designed to be output neutral and in conformance with the principles and the data elements of ISAD(G) and DA:CS. The Toolkit will support a number of standard outputs, including EAD, MARC XML, Dublin Core, OAI, MODS, METS, and limited technical metadata records for digital files. Technical metadata elements are to be based on the NISO MIX standard and PREMIS Data Dictionary. Scope The Toolkit's description module will: Support single- and multi-level description of archival resources. Support single- and multi-level description of archival surrogates. Allow accession information stored in AT accession records to be imported into a resource record. At any descriptive level, allow the user to add numerous descriptive notes fields at the point of need. The AT will provide twenty-seven descriptive note types that Description Functional Area: Overview Page:2

4 can not be repeated and a repeatable general note that the user can define on a case by case basis. Allow surrogates, digital and analog (text; cartographic; notated music; sound recording-musical; sound recording-nonmusical; sound recording; still image; moving image; three dimensional object; software, multimedia; mixed material) to be attached to a resource description at any level. Provide the means for expressing digital objects in finding aids and referencing in the digital objects the place where they are described in a finding aid in order to facilitate reciprocal linking between a digital object and its finding aid. Provide screen representations of resource and surrogate record intellectual arrangement and provide drag and drop editing capabilities. Provide screen representations of a resource s physical arrangement and provide drag and drop editing capabilities. The Toolkit's description module will not: Support extensive technical metadata for digital formats other than text and images. Allow creation of resource component records or surrogate records or surrogate component records without a resource record. Provide functionality for managing, searching, and presenting descriptive outputs such as EAD, MARC, METS, OAI, etc. Description Functional Area: Overview Page:3

5 D2: Description Functional Area: Resources D2.1: Description Record Types An archival resource is 1) an item or aggregate of items generated by an individual, family, or organization in the course of their activities and deemed to be of enduring value, 2) and is in the custody of an archival repository. The AT provides two basic record types for describing archival resources: resource records and resource component records. A resource record can represent one of two types of resources, collections or independent items, that is, items that are not part of a larger aggregation. Either of these types of resource records can stand on their own to form a single-level description. In the case of the collection type of resource record, the resource record may also be linked to resource component records to form multi-level descriptions. Resource component records utilize one of four templates: subdivision (including a repeatable second subdivision), file, and item (that is, an item within an aggregation). Hierarchical Levels These two record types and their associated templates accommodate the twelve levels of description permitted in the Encoded Archival Description standard. In other words, an archival resource described in the AT may be represented by up to twelve hierarchical levels of records. A resource record may be the parent of a component resource record that is parent to a component resource record that is parent to a component resource record, and so on up to twelve levels deep. There may be an unlimited number of component resource records at each level, that is, there is no limit on the number of series records or file records. Records at the same level are referred to as sibling records. EAD provides a standardized vocabulary of labels for the permitted hierarchical levels in an archival resource. These labels (class, collection, file, fonds, item, otherlevel, record group, series, subfonds, subgroup, subseries) each correspond, or map, to one or more of the AT resource or resource component records (See Table 1). When the operator chooses to add a new resource component record to an existing resource or to a component resource record in the Toolkit, she or he is prompted to choose a level label for the component resource. The options given the operator are driven by a set of rules for acceptable children for a given level. For example, the parent of a subseries can be a series, but not a collection. (See Table 2) Description Functional Area: Resources Page:4

6 Record Relationships In addition to the hierarchical relationships between resource and component resource records, the resource and resource component records may also be associated with accession, location, name, subject, and surrogate records, as well as project management records. Table 1 provides a matrix for resource record types, their required elements, possible hierarchical and associative relationships, and their possible labels. Figure 2 is a graphical representation of the various valid hierarchical structures for archival resources. Table 2 delineates the EAD level labels and their valid parents and children in respect to the AT record types. Description Functional Area: Resources Page:5

7 Record Type Required Elements Relationships Labels Parent Child Associated Resource Type of resource record Type of material format (if an item) Resource ID Title Date note and/or date start Extent Conditions governing access Language code Languages and scripts note Scope and contents note None Subdivision File Item Location; Accession; Name as source, subject, or creator; Subject, Surrogate; [Project Management Records] Subdivision Sub-subdivision (recursive) File Level label Subdivision identifier Title Date note and/or date start Extent Level label Subdivision identifier Title Date note and/or date start Extent Level label Title and/or date information (date start and/or date expression) First container number and type Resource Subdivision Sub-subdivision Resource Subdivision Sub-subdivision Sub-subdivision File Item Sub-subdivision File Item Item Name as subject or creator; Subject; Surrogate Name as subject or creator; Subject; Surrogate Name as subject or creator; Subject, Surrogate Collection Fonds Record Group Item Subfonds Subgroup Series Class Otherlevel Series Class Subseries Otherlevel File Otherlevel Component Item Level label Title and/or date information (date start and/or date expression) First container number and first container type or item number Resource Subdivision Sub-subdivision File None Name as subject or creator; Subject; Surrogate Item Otherlevel Table 1. Resource Record Types, Requirements, Relationships, and Labels. Description Functional Area: Resources Page:6

8 Record Type Label Parents Children Collection None Subfonds Subgroup Series Class Record Group None Subgroup Resource Series Class Fonds None Subfonds Series Class Item None None Subdivision/ Sub-subdivision File Item Operator- Selected (Independent) Subfonds Subgroup Series Class Subseries File Item (Component) Collection Fonds Collection Record Group Collection Record Group Fonds Collection Record Group Fonds Series Class Collection Record Group Fonds Subfonds Subgroup Collection Record Group Fonds Subfonds Subgroup Table 2. Level labels, with valid labels for parents and children. Description Functional Area: Resources Otherlevel Otherlevel Subfonds Subgroup Otherlevel Subfonds Subgroup Otherlevel Subseries Otherlevel Series Class Subseries Otherlevel Series Class Subseries File Otherlevel Series Class File Series Class File Subseries File Subseries File Subseries File Item None Otherlevel Any Any File Item Otherlevel File Item Otherlevel File Item Otherlevel Item Otherlevel Item Otherlevel Item Otherlevel Item Otherlevel Item Otherlevel Otherlevel Page:7

9 Figure 2. Hierarchical relationships for aggregate archival resources. Description Functional Area: Resources Page:8

10 Intellectual and Physical Order of Archival Resources Description of archival resources is complicated by the fact that the intellectual order of a resource need not be the same as the resource s physical order. Indeed, there are advantages and efficiencies to be gained by keeping them separate. Accordingly, the Toolkit will support these two orders in a manner that allows the operator to toggle or switch from the representation of the intellectual order to the representation of the physical order, or vice versa. Intellectual hierarchy in the Toolkit will be captured by tracking the relationship of the resource records and component resource record(s) to each other. Both parent/child record linkages and sibling record sequences must be captured and stored. Physical arrangement will be tracked using information in the container fields and / or item identifier. Sorting on container and item identifier information will be complicated by a number of archival practices that should be taken into account where possible, given the availability of limited resources. These include the use of non-numeric values for ordinating containers (e.g., 2A, 2B); entering a single record for a range of folders (e.g., 1-3); use of non-numeric values for unusual containers (e.g., MC5 for map case, Folio 3); and the creation of box lists that list the contents of each box, but without individual folder numbering. If possible given programming time and resources, the AT will also provide an interface for viewing and manipulating both intellectual hierarchy and physical arrangement. The operator will be able to display a visual representation of the intellectual hierarchy or physical arrangement of the resource, and will have the option of toggling between these two views. When viewing the hierarchy or arrangement, she/he will be able to: Collapse and expand record nodes Open a record by selecting the corresponding node in the display of hierarchy or arrangement Modify the sequence and structure of the intellectual hierarchy using a drag and drop technique, including changing the sequence of nodes, promote / demote nodes, and auto-renumber sequences of intellectual units in accord with the modifications D.2.2: Business Rules 1. Every archival resource represented in the database must have a resource record. 2. Every resource record must have a unique Resource ID. 3. A resource record may represent one of two types of resources: 1) a collection, or 2) an item. Description Functional Area: Resources Page:9

11 4. A resource record for an item may not have component resource records. 5. A resource record for a collection may, but need not, have component resource records. 6. A collection may accommodate up to twelve hierarchical levels of component resource records, in compliance with the EAD specification. 7. A record for a component resource (subdivision, file, etc.) cannot exist in the database without being linked to a resource record. 8. To maintain the proper hierarchical structure, the following rules will be established: a. The parent of a subdivision record must be a resource record. b. The parent of a second subdivision record may be a subdivision record or second subdivision record, etc. c. The parent of a file record may be a resource, subdivision, or second subdivision record. d. The parent of a component item record may be a resource, subdivision, second subdivision, or file record. e. A component item record cannot have any child records 9. The repository s customized input templates for aggregate resources and component resources (collections, subdivisions, files) may differ. For example, the conditions governing access note may commonly be included in the input template for resource and subdivision records, but not in the template for a file record. An operator with appropriate permissions, however, will have the option of adding any element from the aggregates metadata palette to the record as needed. Thus, the full set of descriptive elements for aggregates is available at any point in the hierarchy even if they do not appear on the input template established by the repository. 10. Resource records may inherit some data from accession records and link to location records and name as source records. 11. Resource records and resource component records may link to subject records, name as subject records, and name as creator records. Description Functional Area: Resources Page:10

12 D2.3: Required and Optional Tasks Sequences Note: Requirements draw upon on DA:CS and MARC guidelines for minimal records. Resource Record Required Tasks 1. Select option to create a resource record 2. Select type of resource record (collection or item) 3. If item, select object type for the item 4. Select existing resource ID or assign a new resource ID 5. Enter title 6. Enter date expression and/or date start 7. Enter extent 8. Enter conditions governing access 9. Select language code 10. Enter languages and scripts note 11. Enter scope and content note 12. Save record Optional Tasks 1. Change level label to record group or fonds 2. Enter date end 3. Enter bulk date start and bulk date end 4. Enter abstract 5. Indicate that restrictions apply to the resource 6. Enter additional descriptive notes 7. Add name as creator 8. Add name as source Description Functional Area: Resources Page:11

13 9. Add name(s) as subject 10. Add subject terms 11. Add, edit, or remove location records linked to the resource record 12. Add component resource record to the resource record 13. Add a surrogate record at this level Subdivision Record (This also applies to Sub-subdivision record, except Sub-subdivision record requires existence of a subdivision.) Required Tasks 1. From resource or other subdivision record, select option to add a component resource record 2. Select level label for the component resource 3. Enter subdivision identifier 4. Enter title 5. Enter date note and/or date start 6. Enter extent Optional Tasks 1. Enter date end 2. Enter bulk date start and bulk date end 3. Enter scope and contents note 4. Enter additional descriptive notes 5. Indicate that restrictions apply to the resource 6. Add component resource record to this record 7. Add name record (creator or subject) 8. Add subject term record 9. Add a surrogate record to this record Description Functional Area: Resources Page:12

14 File Record 10. Add a sibling subdivision record Required Tasks 1. From resource or subdivision record, select option to add a component resource record 2. Select level label for the component resource 3. Enter title and/or date information (date start and/or date note) 4. Enter container 1 type and container 1 first container id 5. Save record Optional Tasks 1. Enter date end 2. Enter bulk date start and bulk date end 3. Enter container 1 second container id 4. Enter container 2 type, container 2 first container id, and container 2 second container ID 5. Enter additional descriptive notes 6. Indicate that restrictions apply to the resource 7. Add component resource record to this record 8. Add name record 9. Add subject term record 10. Add a surrogate record to this record 11. Add a sibling file record Component Item Record Required Tasks 1. From resource, subdivision, or file record, select option to add a component resource record Description Functional Area: Resources Page:13

15 2. Select level label for the component resource 3. Enter title and / or date expression or begin date 4. Enter container 1 type and container 1 first container id, or item number 5. Save record Optional Tasks 1. Enter container 1 second container id 2. Enter container 2 type, container 2 first container id, and container 2 second container ID 3. Enter item label 4. Select object type for the item 5. Enter additional descriptive notes 6. Indicate that restrictions apply to the resource 7. Add name record 8. Add subject term record 9. Add a surrogate record to this item 10. Add a sibling item record D2.4: User intentions / Application response sequence User Intentions (Required in Italics) Primary Secondary Create a resource record From Description Main Menu select option to create a new resource record Select level label Application Response / Action Prompt operator to select a level label (collection, fonds, record group, item) Display resource template with repository default elements and repository name in Description Functional Area: Resources Page:14

16 If item, enter object type breadcrumbs Link to existing resource ID or enter resource ID Link accessions with this resource Enter a search name Select an accession title to use for this record Provide operator with search box for accession records List titles of accession records matching the search term Populate resource record with Resource ID, title, and all linked name, subject, and location records from accessions linked to this resource ID Enter or edit title Enter date note and/or date start Enter date end Enter bulk date start and bulk date end Enter extent and select extent type Enter conditions governing access Select language code Enter languages and scripts note Description Functional Area: Resources Page:15

17 Enter scope and content note Enter abstract Enter sponsor note Indicate that restrictions apply to this resource Select option to save resource record System does not respond except for when other record creation processes are activated. All input data is displayed in its frame. If required fields are not completed, indicate that the record cannot be saved because one or more required fields are not completed. Highlight the required fields that need to be completed. If required fields are completed, prompt the operator to set the description status of the resource (and its component resources, if any) The following tasks are completed with a resource record open and saved. The required secondary tasks are only required if the primary task is exercised. Add descriptive notes Select option to add note Indicate note type Enter note Machine displays note template Description Functional Area: Resources Save note Machine checks to see Page:16

18 Add/remove Name record (creator, subject, or source) to resource record Add/remove Subject record to resource record Add/remove location record to resource record Add resource component record (for collections, fonds, or record groups only) Operator chooses to add or remove a name as creator, name as subject, or name as source to the resource record Operator chooses to add or remove a subject to the resource record Operator chooses to add or remove a location record to the resource record From a saved resource record, select option to add a resource component record that a note type has been selected and content entered into the note field. If not, machine responds note cannot be saved. Otherwise, machine responds note is saved. Saved note is displayed, with type label, as part of the resource record Name selection or removal process is started Subject selection or removal process is started Location creation or deletion process is started Resource component description process is started (see subdivision, Description Functional Area: Resources Page:17

19 Add Surrogate record (from any record) Subdivision Record From any saved description record, the operator chooses to add a surrogate record file, and item component grids below) Surrogate description process is started User Intentions (Required in Italics) Primary Secondary Create a resource From resource record or component record other subdivision record, select option to add a resource component record Application Response / Action Prompt operator to select a level label for the child of a COLLECTION (subfonds, subgroup, series, class, file, item, otherlevel) ; FONDS (subfonds series, class, file, item, otherlevel) ; RECORDGROUP (subgroup, series, class, file, item, otherlevel) ; SUBFONDS (series, class, file, item, otherlevel) ; SUBGROUP (series, class, file, item, otherlevel); SERIES (subseries, file, item, otherlevel) ; CLASS (subseries, file, item, otherlevel) ; SUBSERIES (subseries, file, item, otherlevel); or OTHERLEVEL (if otherlevel was a subdivision type record, then children could be subfonds, subgroup, series, class, subseries, Description Functional Area: Resources Page:18

20 Select level label (subfonds, subgroup, series, class, subseries, or otherlevel) If otherlevel was selected, enter a label for the otherlevel and select the subdivision template Enter subdivision identifier file, item, otherlevel) If operator chooses otherlevel, prompt for a label for the otherlevel, and the template to be used (subdivision or file) Display subdivision template with repository default elements and repository name, resource ID, resource title, and resource date, (and any parent subdivision titles and dates) in breadcrumbs Enter subdivision title Enter subdivision date note and/or date start Enter subdivision date end Enter subdivision bulk date start and bulk date end Enter subdivision extent and select extent type Enter scope and content note Indicate that restrictions apply to this resource Description Functional Area: Resources Page:19

21 Select option to save resource component record System does not respond except for when other record creation processes are activated. All input data is displayed in its frame. If required fields are not completed, indicate that the record cannot be saved because one or more required fields are not completed. Highlight the required fields that need to be completed. If required fields are completed, prompt the operator to set the description status of the resource (and its component resources, if any) The following tasks are completed with a resource component record open and saved. The required secondary tasks are only required if the primary task is exercised. Add descriptive notes Select option to add note Indicate note type Enter note Save note Machine displays note template Machine checks to see that a note type has been selected and content entered into the note field. If not, machine responds note cannot be saved. Description Functional Area: Resources Page:20

22 Add/remove Name record (creator or subject) to resource record Add/remove Subject record to resource record Add component record Add Surrogate record (from any record) File Record Operator chooses to add or remove a name as creator or name as subject to the resource record Operator chooses to add or remove a subject to the resource record From a saved resource component record, select option to add a component record From any saved description record, the operator chooses to add a surrogate record Otherwise, machine responds note is saved. Saved note is displayed, with type label, as part of the resource record Name selection or removal process is started Subject selection or removal process is started Component description process is started (see file and item component grids below) Surrogate description process is started User Intentions (Required in Italics) Primary Secondary Create a resource From resource record or component record subdivision record, select option to add a Application Response / Action Description Functional Area: Resources Page:21

23 resource component record Select level label (file or otherlevel) If otherlevel was selected, enter a label for the otherlevel and select the file template Prompt operator to select a level label for the child of a COLLECTION (subfonds, subgroup, series, class, file, item, otherlevel) ; FONDS (subfonds series, class, file, item, otherlevel) ; RECORDGROUP (subgroup, series, class, file, item, otherlevel) ; SUBFONDS (series, class, file, item, otherlevel) ; SUBGROUP (series, class, file, item, otherlevel); SERIES (subseries, file, item, otherlevel) ; CLASS (subseries, file, item, otherlevel) ; SUBSERIES (subseries, file, item, otherlevel); or OTHERLEVEL (if otherlevel was a subdivision type record, then children could be subfonds, subgroup, series, class, subseries, file, item, otherlevel) If operator chooses otherlevel, prompt for a label for the otherlevel, and the template to be used (subdivision or file) Display file template with repository default elements and repository name, resource ID, Description Functional Area: Resources Page:22

24 Enter file title and/or file date information (date start and/or date note) resource title, resource date, and any parent subdivision titles and dates in breadcrumbs Enter file date end Enter file bulk date start and bulk date end Enter container 1 type Enter container 1 first container id Enter container 1 second container id Enter container 2 type Enter container 2 first container id Enter container 2 second container id Description Functional Area: Resources Indicate that restrictions apply to this resource Select option to save resource component record System does not respond except for when other record creation processes are activated. All input data is displayed in its frame. If required fields are not completed, indicate that the record cannot be saved because one or more required fields are not completed. Highlight Page:23

25 the required fields that need to be completed. If required fields are completed, prompt the operator to set the description status of the resource (and its component resources, if any) The following tasks are completed with a resource component record open and saved. The required secondary tasks are only required if the primary task is exercised. Add descriptive notes Add/remove Name record (creator or subject) to resource record Select option to add note Indicate note type Enter note Save note Operator chooses to add or remove a name as creator or name as subject to the resource record Machine displays note template Machine checks to see that a note type has been selected and content entered into the note field. If not, machine responds note cannot be saved. Otherwise, machine responds note is saved. Saved note is displayed, with type label, as part of the resource record Name selection or removal process is Description Functional Area: Resources Page:24

26 Add/remove Subject record to resource record Add component record Add Surrogate record (from any record) Component Item Record Operator chooses to add or remove a subject to the resource record From a saved resource component record, select option to add a component record From any saved description record, the operator chooses to add a surrogate record started Subject selection or removal process is started Component description process is started (see file and item component grids below) Surrogate description process is started User Intentions (Required in Italics) Primary Secondary Create a resource From resource record, component record subdivision record, or file record, select option to add a resource component record Application Response / Action Prompt operator to select a level label for the child of a COLLECTION (subfonds, subgroup, series, class, file, item, otherlevel) ; FONDS (subfonds series, class, file, item, otherlevel) ; RECORDGROUP (subgroup, series, class, file, item, otherlevel) ; SUBFONDS (series, class, file, item, Description Functional Area: Resources Page:25

27 Select level label (item) Enter object type otherlevel) ; SUBGROUP (series, class, file, item, otherlevel); SERIES (subseries, file, item, otherlevel) ; CLASS (subseries, file, item, otherlevel) ; SUBSERIES (subseries, file, item, otherlevel); FILE (item, otherlevel); or OTHERLEVEL (if otherlevel was a subdivision type record, then children could be subfonds, subgroup, series, class, subseries, file, item, otherlevel; if otherlevel was a file type record, then children could be item, otherlevel) Display item template with repository default elements and repository name, resource ID, resource title, resource date, any parent subdivision titles and dates, and any parent file container information, title, and dates in breadcrumbs Enter item title and/or item date information (date start and/or date note) Enter item date end Enter item bulk date start and bulk date end Enter container 1 type and first container ID OR Description Functional Area: Resources Page:26

28 item number Enter container 1 second container id Enter container 2 type Enter container 2 first container id Enter container 2 second container id Enter item label Indicate that restrictions apply to this resource Select option to save resource component record System does not respond except for when other record creation processes are activated. All input data is displayed in its frame. If required fields are not completed, indicate that the record cannot be saved because one or more required fields are not completed. Highlight the required fields that need to be completed. If required fields are completed, prompt the operator to set the description status of the resource (and its component resources, if any) The following tasks are completed with a resource component record open and saved. The required secondary tasks are only required if the primary task is exercised. Description Functional Area: Resources Page:27

29 Add descriptive notes Add/remove Name record (creator or subject) to resource record Add/remove Subject record to resource record Add component record Select option to add note Indicate note type Enter note Save note Operator chooses to add or remove a name as creator or name as subject to the resource record Operator chooses to add or remove a subject to the resource record From a saved resource component record, select option to add a component record Machine displays note template Machine checks to see that a note type has been selected and content entered into the note field. If not, machine responds note cannot be saved. Otherwise, machine responds note is saved. Saved note is displayed, with type label, as part of the resource record Name selection or removal process is started Subject selection or removal process is started Component description Description Functional Area: Resources Page:28

30 Add Surrogate record (from any record) From any saved description record, the operator chooses to add a surrogate record process is started (see file and item component grids below) Surrogate description process is started D2.5: Inputs Resource Identifier Level Label Date Begin Date End Bulk Date Begin Bulk Date End Date Expression Title Extent Restrictions Apply Abstract Language of Materials Code Sponsor Note Subdivision Identifier Container 1 Type Container 1 First Container ID Container 1 Second Container ID Container 2 Type Container 2 First Container ID Container 2 Second Container ID Object Type Item Number Item Label Note Content Note Type Options: o Extent description o Dimensions o Conditions Governing Access o Conditions Governing Use o Language of Materials Note o Biographical/Historical Note Description Functional Area: Resources Page:29

31 o Scope and Contents Note o Organization Note o Arrangement Note o Physical Characteristics and Technical Requirements o Publication Note o Finding Aids o Existence and Location of Copies o Related Archival Materials o Separated Materials Note o Custodial History o Immediate Source of Acquisition o Appraisal Note o Accruals Note o Existence and Location of Originals o Processing Information o Contributors Note o General Physical Description o Location Note o Material Specific Details o Physical Facet o Legal Status o General Note Description Functional Area: Resources Page:30

32 D2.6 Data Flow Diagrams Resource Data Flow Diagram Description Functional Area: Resources Page:31

33 Description Functional Area: Resources Page:32

34 Description Functional Area: Resources Page:33

35 Description Functional Area: Resources Page:34

36 Description Functional Area: Resources Page:35

37 Description Functional Area: Resources Page:36

38 Description Functional Area: Resources Page:37

39 Description Functional Area: Resources Page:38

40 Description Functional Area: Resources Page:39

41 Subdivision Data Flow Diagram Description Functional Area: Resources Page:40

42 Description Functional Area: Resources Page:41

43 Description Functional Area: Resources Page:42

44 Description Functional Area: Resources Page:43

45 Description Functional Area: Resources Page:44

46 File Data Flow Diagram Description Functional Area: Resources Page:45

47 Description Functional Area: Resources Page:46

48 Description Functional Area: Resources Page:47

49 Description Functional Area: Resources Page:48

50 Description Functional Area: Resources Page:49

51 Description Functional Area: Resources Page:50

52 Item Data Flow Diagram Description Functional Area: Resources Page:51

53 Description Functional Area: Resources Page:52

54 Description Functional Area: Resources Page:53

55 Description Functional Area: Resources Page:54

56 Description Functional Area: Resources Page:55

57 Description Functional Area: Resources Page:56

58 D2.7: Screen Sequences Resource Screen Sequence s Description Functional Area: Resources Page:57

59 Description Functional Area: Resources Page:58

60 Description Functional Area: Resources Page:59

61 Description Functional Area: Resources Page:60

62 Description Functional Area: Resources Page:61

63 Description Functional Area: Resources Page:62

64 Description Functional Area: Resources Page:63

65 Description Functional Area: Resources Page:64

66 Description Functional Area: Resources Page:65

67 Description Functional Area: Resources Page:66

68 Description Functional Area: Resources Page:67

69 Description Functional Area: Resources Page:68

70 Subdivision Screen Sequences Description Functional Area: Resources Page:69

71 Description Functional Area: Resources Page:70

72 Description Functional Area: Resources Page:71

73 Description Functional Area: Resources Page:72

74 File Screen Sequences Description Functional Area: Resources Page:73

75 Description Functional Area: Resources Page:74

76 Item Screen Sequences Description Functional Area: Resources Page:75

77 Description Functional Area: Resources Page:76

78 D3: Description Functional Area: Surrogates D-3.1: Description The is designed to support description of surrogates of archival items. A surrogate is an entity that 1) is a copy--analog or digital, in full or in part--of an item contained in archival resource and 2) that is located, accessed, and managed outside the archival resource. For instance, an archival resource may contain an 8 x 10 photoprint of a building. The negative for that photoprint may be stored in a cumulative collection of negatives. Or an archival resource may contain a brittle copy of a 17 th century diary. A photocopy of the diary may be cataloged as a monograph, shelved with a repository s book collections, and offered for use in the place of the original. Or, finally and increasingly so, an archival resource may contain an item which has been digitized and is available independent of the archival resource that contains the original item. Of the two criteria, the second is the most important. A surrogate of an item in an archival resource and that is itself also contained in the archival resource and reflected in the description of that resource is to be treated as a component of the archival resource and not as a surrogate. Thus, if the photocopy of the diary were contained in the archival resource, then it should be described as a component of that archival resource according to the descriptive conventions of the custodial repository. The AT is designed to output surrogate descriptions conforming to this definition both as related parts of archival resource descriptions and as autonomous object descriptions in their own right. That is, the AT will facilitate building digital objects in a manner that supports linking surrogate descriptions to finding aids on the one hand, and, on the other, producing autonomous digital object descriptions that can interoperate with other autonomously described entities. The AT digital object descriptions will carry with them contextual information that relates each digital object to its proper archival resource context and will facilitate linking directly to that context. In addition, the digital object descriptions can be created to include technical metadata to support, at the very least, rudimentary preservation management of the digital objects. Creation / Application Process for Surrogate Records Surrogate records: Surrogate records are created within the context of a resource or resource component record. A surrogate record may be linked to only one resource or resource component record; however, more than one surrogate record may be linked to the same resource or resource component record. It is assumed that the resource or resource component record to which a surrogate record is linked either explicitly or implicitly describes the source of the surrogate. An Description Functional Area: Surrogates Page:77

79 explicit description occurs when nearly a one to one correspondence exists between the material described in the resource or resource component record and the material described in the surrogate record. For instance, the resource component record might describe a photoprint and the surrogate record might describe a digital version of the photoprint. An implicit description occurs when a group of materials, say a number of photographic portraits, are described in the resource or resource component record, while what is described in the surrogate record is one member or item within that group. In such instances, the surrogate record will provide more detailed and granular description. In order to save a surrogate record, the operator must indicate if the surrogate is an analog or digital object. An example of an analog object would be a microfilm of some object or collection of objects in the archival resource that is stored and managed outside of the archival resource. An example of a digital object would be one or more electronic files that duplicate or copy some object or collection of objects in the archival resource and that is also stored and managed outside of the archival resource. If the analog or digital copies are stored inside and managed as part of the archival resource, then they should be described using resource or resource component records. In addition, the operator must indicate the object type, picking a term from the provided list of object types. Besides these two data elements, the surrogate record inherits four other data elements from the resource or resource component record to which it is linked. It inherits the title of the material as described in the resource or resource component record, and it inherits the container information, if it exists, expressed in the related resource or resource component record. These two data elements can be edited or replaced by the operator. In addition, the surrogate record inherits the resource title and the resource id. These two elements cannot be edited or replaced in the surrogate record, as they reflect the basic context for the surrogate. The operator will have the ability to include several optional data elements in the surrogate record. These include: language indicator, date expression and begin / end date terms, and whether or not restrictions apply to the surrogate. In addition, there will be the ability to add an unconstrained number of notes, utilizing a note sub-routine, which allows the operator to indicate the type of note and content of the note. Finally, the surrogate record may be associated with other records in the AT. Name records for names as creators and subjects may be linked to the surrogate record, as may subject term records. Location records and accession records may not be linked to the surrogate records. If the surrogate is an analog object, it can not be described beyond the surrogate record. In other words, for any one analog surrogate object there can be one and only one surrogate record. Description Functional Area: Surrogates Page:78

80 Surrogate component records: If, however, the surrogate is a digital object, then the operator may create surrogate component records to describe the parts of the digital surrogates, that is, the files that comprise the digital surrogate. It is not a requirement to create surrogate component records for digital surrogates; however, the surrogate component records are necessary for using the AT to produce valid METS digital objects and, moreover, digital objects containing sufficient technical metadata to support preservation management. If a surrogate component record is created, it must link, directly or indirectly via another surrogate component record, to one and only one surrogate record. One or more surrogate component records can link to the same higher level surrogate component record or directly to the surrogate record. A surrogate component record is created to describe a part or division of a digital surrogate, and, to exist in the AT, it must describe that part in three respects. The surrogate component record must indicate if the part is a physical or logical part of the surrogate. A page or volume are examples of physical parts of a surrogate, whereas entry or chapter are examples of logical parts. In addition, the surrogate component record must indicate the label to be used for the part, that is, that the physical part is a page or a volume or something else. The AT prescribes the use of a label but not the content of a label. Finally, the surrogate component record must indicate the sequential relationship the part described has to other parallel parts. Thus, if pages were being described, then the operator would have to indicate what is the first page, what is the second page, and so forth. Beyond these requirements, the operator can add numerous optional data elements. These include a title for the surrogate part, if it is different from the title expressed for the surrogate as a whole. This is not uncommon for digital surrogates such as scrapbooks. Other options are to indicate the language of the part and date for the part; and to add descriptive notes, using the same note sub-routine described for the surrogate record. Like the surrogate record, the surrogate component record can be linked to one or more name as creator, name as subject, and subject records. Unlike the surrogate record, the surrogate component record has three other options. One is to create another surrogate component record at the same level. The second is to create a surrogate component record at a lower level, that is, to divide the parts into sub-parts. For instance, a diary might be divided into high level parts equal to volumes of the diary. The volumes might be divided into years. The years might be divided into entries. And the entries might be divided into pages. The third option is to itemize the digital file version(s) representing the part. Description Functional Area: Surrogates Page:79

81 Itemizing digital file versions The AT does not require itemization of file versions for digital surrogates, but such itemization is necessary for producing digital object metadata compliant with the METS schema. Versions of digital files occur when the surrogate part is rendered multiple times using slightly different file formats to support different functions or objectives. To use a classic illustration, a TIFF is created to produce the highest quality digital image of an object. Because TIFFs require considerable bandwidth for real time delivery, a lower resolution JPEG may be created for delivering a usable image to the end user. And to support the ability to display a number of images side by side, a lower resolution GIF image may be created. All three images are versions of the same surrogate part. The basic relationship in this chain of versions is that a high quality, archival master version to a lower quality, quicker to serve, user copy. This relationship can hold for image, audio, and video files. It is less typical of text files. There are three basic steps for itemizing digital file versions for digital surrogates in the AT, which are to be repeated for each file version listed as a surrogate part. The first step is to identify the files. This step requires indicating the type of file: application, audio, image, text, or video. It also requires indicating the file group to which the version belongs. Each file group is to be composed of digital versions of the same part. Thus, a TIFF, JPG, and GIF for the same surrogate part would be contained in the same file group. To put it differently, typically all digital files itemized for a surrogate component record will likely share the same file group. Last, the file name, with or without location information, must be entered. File names can be conventional or in the form of persistent identifiers (PIDs) such as ARKs and handles. Once basic identification of the digital file is complete, the operator has the choice to record core technical metadata for the digital file. These metadata elements are format identification, file size, checksum, checksum method, and date of creation. These elements can be recorded generically for any kind of digital file, and they will support very basic preservation management functions. The operator will also have the option to add extended technical metadata for each category of file types. That is, the operator can select an option to provide additional technical metadata for image files, or select another option to provide additional technical metadata for text files, and so on. This additional technical metadata is more specific to the category of file type and, in the case of image files, is based on the NISO MIX schema for describing still images. For its first release, the AT will only support extended technical metadata for images and for text, and not for video or audio file types. The AT will support manual data entry for technical metadata. If resources are available, effort will be made to make use of various open source tools for automating the extraction and recording of technical metadata. For instance, open source checksum tools might be used to produce the checksum value in the basic technical Description Functional Area: Surrogates Page:80

82 metadata. And a metadata extraction tool such as JHOVE might be used for extracting the more extended technical metadata for image and text files (and for other file types as JHOVE matures). Providing such tools will encourage repositories to collect the technical metadata and construct better formed digital objects. Below are two diagrams illustrating the various possible parts of the surrogate record chain. The first diagram represents a diary composed of image files for two diary pages and a corresponding text file for the entire diary. The diagram represents technical metadata being captured for only the TIFF archival master, as well as the text file. But technical metadata could also be recorded for the JPEG and GIF image files, if deemed desirable. The second diagram illustrates an oral history surrogate for which there are three digital file versions. Core technical metadata can be recorded for all three versions; however, the application in its first release will only support capturing extended technical metadata for image and text files. Description Functional Area: Surrogates Page:81

83 D-3.2: Business Rules 1: The AT will support the descriptions of surrogates, which 1) are complete or partial copies of an item contained in an archival resource and 2) are not themselves housed and otherwise described as part of the archival resource. 2: Surrogates are described using surrogate records and surrogate component records. 3: The surrogate record and surrogate component record provides for the same general descriptive capabilities as do the resource item record and the resource component item record. 4: The surrogate record is for describing the surrogate as a whole. Description Functional Area: Surrogates Page:82

84 4a: The surrogate record must indicate if the surrogate is an analog item or a digital item. 4a1: If the surrogate is a digital item, then surrogate component records are provided to support the description of the individual files comprising the digital item, as such description is necessary for producing a well-structured and useful METS record and for assuring accurate rendering of the digital files. 4a2: If the surrogate is an analog entity, then the use of component records will not be permitted, and the surrogate item will be completely described using only the surrogate record. 4b: Surrogate records, to exist in the AT, must link to a resource record. 4b1: A surrogate record must link to one and only one resource record or resource component record at any level. It is expected a surrogate record will be linked to the resource record or, more likely, resource component record that explicitly or implicitly describes the archival item that is the source of the surrogate. 4b2: More than one surrogate record may be linked to a certain resource or resource component record. 4c: The surrogate record shall accommodate information allowing for jumping from an output version of the surrogate record (METS, Dublin Core, etc.) to the place in an output version of the resource record (e.g., finding aid) where the surrogate is described explicitly or implicitly. 5: Surrogate component records are for describing the components (files or parts) comprising a digital surrogate. 5a: The surrogate components represent parts of a digital surrogate. They are like entries in a diary or pages in a book. 5b: Each surrogate component record must indicate the part type (page, entry, volume, etc) represented by the component part, in other words, sibling parts. 5c: Each surrogate component record must indicate the sequence of the component part within all the surrogate component records at the same level 5d: Surrogate component records may be extended or sub-divided indefinitely, allowing for a rich hierarchical representation of a complex digital object comprised of many digital files. 5d1: Each surrogate component record may be coupled to an indefinite number of sibling records, that is, surrogate component records at the same level. Description Functional Area: Surrogates Page:83

85 5d2: Each surrogate component record may be divided infinitely by additional component records. 5e: Surrogate component records, to exist in the AT, must be linked to a surrogate record describing a digital surrogate or to another surrogate component record that is linked to a surrogate record describing a digital surrogate. A surrogate component record that does not resolve to a surrogate record describing a digital surrogate is not permissible in the AT. 5e1: A surrogate component record must be linked to one and only surrogate record or surrogate component record. 5e2: One or more surrogate component records may be linked to the same surrogate record or surrogate component record. 6: Each surrogate component record may represent one or more versions, e.g., file formats, of the component part of the surrogate. A single image, for example, may be represented by a high resolution TIFF (archival master copy), a medium resolution JPEG (end user copy), and a low resolution GIF or JPEG (thumbnail reference copy) 6a: Versions of a surrogate component part are expressed as file (locations and names) in the surrogate component record to which they apply. 6b: Each version must be described as being either an image, audio, video, text, or application file format. Indicating the file type establishes the type of format available for capturing extended technical metadata. 6c: Each version of a surrogate component part may have a use label expressed for it. That is, a TIFF image may have the use label archival master, whereas a JPG version of the same image may have the use label reference image. 6d: Every surrogate component record for a part of that digital surrogate must reference at least one version, e.g. file format in order to produce a valid METS document representing the digital surrogate. 6e: For any version (e.g., file) of a surrogate component part, there will be an option, but not a requirement, to provide core technical metadata descriptive of the version (file format). 6f: There will be an option to provide additional, more specific, technical metadata for image and text files. 6g: Capture of specific technical metadata for audio and video file formats will not be supported in this version of the AT. Description Functional Area: Surrogates Page:84

86 D-3.3: Required Tasks Sequence for Surrogate Record Select option to create surrogate record Create surrogate object number (done automatically) Indicate if surrogate is an analog or digital object Indicate object type Inherit title (providing for editing / replacement) Inherit Resource Title from linked resource record (do not allow editing or replacement) Inherit Resource ID from linked resource record (do not allow editing or replacement) Inherit container information from resource record (providing for editing / replacement) Save surrogate record D-3.4: Optional Tasks Sequence for Surrogate Record Indicate predominant language (if applicable) Add date expression Add begin date Add end date Indicate that restrictions apply Add descriptive note(s)--(contributors, condition, location, access / use, rights, etc.) Add Name record for creator Add Name record for subject Add Subject record Description Functional Area: Surrogates Page:85

87 Add Component record (for digital surrogates only) D-3.5: Required Tasks Sequence for Surrogate Component Record (required only when surrogate component record is created) Select option to add surrogate component record (available only for digital surrogates) Indicate component arrangement type: physical or logical Indicate part label: e.g., volume, page, entry, etc. Indicate part sequence in relationship to other parts at same level, e.g., page 1, page 2, page 3, etc. Save surrogate component record D-3.6: Optional Tasks Sequence for Surrogate Component Records Enter title (if different from title in surrogate record) Indicate predominant language (if applicable) Add date expression Add begin date Add end date Add descriptive note(s)--(contributors, condition, location, access / use, rights, etc.) Itemize for Digital File Version(s) Add Name record for creator Add Name record for subject Add Subject record Add Surrogate Component record at same level Add Surrogate Component record at sub-level Description Functional Area: Surrogates Page:86

88 D-3.7: Required Tasks for Itemizing Digital Files Indicate digital file type: application, audio, image, text, video Indicate file group (Group 1, Group 2, etc.). Each file group includes all the parts of the same version. Indicate file name, with or without location (PIDs, such as ARKs and handles, are permissible) Save Itemized File record D-3.8: Optional Tasks for Itemizing Digital Files Enter use label for digital file, e.g. master, reference, thumbnail for images. Add Technical description for digital file version(s) D-3.9: Required Tasks for Technically Describing Itemized Digital Files Indicate for all digital file versions: Format Identification File size Checksum Checksum method Date of Creation D-3.10: Optional Tasks for Technically Describing Itemized Digital Image Type Files Extract the following technical metadata using a metadata extraction application (JHOVE, e.g.), if possible, or provide manually: Mime type Byte order Compression scheme Color space Reference Black White Strip Offsets Rows per Strip Description Functional Area: Surrogates Page:87

89 Strip Byte Counts Planar Configuration Orientation Sampling Frequency Unit X Sampling Frequency Y Sampling Frequency Image Width Image Length Bits Per Sample Samples Per Pixel Indicate manually also: Source type Source ID Image Producer Image Device Type Scanner Manufacturer Scanner Model Name Scanning Software Scanning Software Version Number Processing software D-3.11: Optional Tasks for Technically Describing Itemized Digital Text Files Extract the following technical metadata using a metadata extraction application (JHOVE, e.g.), if possible, or provide manually: Mime type Format D-3.12: User intentions / Application response sequence User Intentions (Required in Italics) Application Response / Action Primary Secondary Create a surrogate record From a resource record or resource component record, select option to create a surrogate record for surrogate item. Surrogate records can only be created within a resource context. Machine returns a template for Description Functional Area: Surrogates Page:88

90 describing a surrogate. Indicate if surrogate is an analog or digital object The template inherits the Resource ID, Resource title, title from linked resource record, and container info from linked resource record. The first two cannot be edited, replaced, or deleted, whereas the second two can be edited or replaced. Machine automatically creates a surrogate object number Select appropriate object type Edit or replace inherited title for surrogate Indicate predominant language Add date expression Add begin date Add end date Indicate if restrictions apply Save surrogate record If not all required elements are completed, machine responds that record can not be saved because required elements are not completed. Elements needing completion are highlighted in the surrogate record template. If all required elements are completed, machine responds that surrogate record has been saved. The following tasks are done with a surrogate record open and already saved. The required secondary tasks are only required if the primary task is exercised Surrogate object number is displayed in resource / resource component record to which surrogate record is linked Description Functional Area: Surrogates Page:89

91 Add descriptive note Link Name record for creator to surrogate record Link Name record for subject to surrogate record Link Subject record to surrogate record Add Surrogate Component Record(s) (for digital surrogates only) Indicate note type Enter note Save note Operator chooses to apply a name as creator record to the surrogate record Operator chooses to apply a name as subject record to the surrogate record Operator chooses to apply a subject term to the surrogate record From a surrogate record or from a surrogate component record (already linked to a surrogate record), the operator chooses to add a surrogate component record. Machine displays note template (surrogate record sub-routine) Machine checks to see that a note type has been selected and content entered into the note field. If not, machine responds note cannot be saved. Otherwise, machine responds note is saved. Saved note is displayed, with type label, as part of the surrogate record Machine asks operator if another note is to be created. If operator says yes, another blank note form is displayed. If operator says no, operator is returned to surrogate record where all saved notes are displayed. Name selection process is started for name as creator Name selection process is started for name as subject Subject term selection process is started. Machine displays a template for describing a surrogate Description Functional Area: Surrogates Page:90

92 component record. The template uses breadcrumbs to show the ascending hierarchical path of surrogate records Indicate component relationship: physical or logical Enter part label Enter part sequence in relationship to other parts at same level Enter title (if different than surrogate) Indicate predominant language Add date expression Add begin date Add end date Save Component Surrogate Record The template inherits the Resource ID, the Resource Title, and the surrogate title from the surrogate record and its relationship to a resource record. If not all required elements are completed, machine responds that record can not be saved because required elements are not completed. Elements needing completion are highlighted in the surrogate component record template. If all required elements are completed, machine responds that surrogate component record has been saved. Surrogate component record number is displayed in surrogate record to which surrogate component record is linked The following tasks are done with a surrogate component record open and already saved. The required secondary tasks are only required if the primary task is exercised Add descriptive note Note process is started Link Name record for creator to surrogate record Operator chooses to apply a name as creator record to the surrogate record Description Functional Area: Surrogates Page:91

93 Link Name record for subject to surrogate record Link Subject record to surrogate record Itemize digital file versions Add Surrogate Component Record at same level Operator chooses to apply a name as subject record to the surrogate record Operator chooses to apply a subject term to the surrogate record With a surrogate component record open and already saved, operator selects option to identify the digital files Operator indicates file group (1 n) Operator indicates use label, e.g., archival master. Operator enters the file name (URL, PID, etc.) Operator indicates file type image, audio, text, video, application Save file identification Name selection process is started for name as creator Name selection process is started for name as subject Subject term selection process is started. Machine returns a template for identifying a single digital file Machine checks to assure that values have been entered for file group and for file name. If not, machine responds file identification can not be saved. Machine also checks to assure that file identification has not already been used for same group. If so, machine responds that file identification is a duplicate. Otherwise, machine responds that file identification has been saved. File name appears in surrogate component record to which file identification is made Machine returns a surrogate Description Functional Area: Surrogates Page:92

94 Add surrogate Component Record at lower level (one step down in hierarchy) Operator follows task sequence for surrogate component records component record template Inheritance principles are the same. Machine returns a surrogate component record template Inheritance principles are the same, with addition that surrogate component record one step above is now reflected in the breadcrumbs Operator follows task sequence for surrogate component records The following tasks are done with a file identification template open and already saved. The required secondary tasks are only required if the primary task is exercised Add core technical metadata Operator selects option to add baseline technical metadata Machine returns a template for entering the baseline technical metadata. The template repeats the breadcrumb sequence of the surrogate component record for which the file identification is made. Enter format identification Enter file size Enter checksum method Enter checksum value Enter date of creation Save technical metadata The template also inherits the file name from the file identification to which the technical metadata is associated. Machine checks that all required elements have values. If an element is missing a value, machine responds that technical data cannot be saved. The element with Description Functional Area: Surrogates Page:93

95 Itemize another file (for same surrogate component record) Operator selects option to indicate another file identification for the open surrogate component record. missing value is highlighted in the template. Otherwise technical metadata is saved. Note: it may be possible to provide tools by which acquisition and recording of the technical metadata is automated. E.g., a plug-in application for checksums. Machine returns a file identification template. Operator follows task sequence for file identification The following tasks are done with a technical metadata template open and already saved. The required secondary tasks are only required if the primary task is exercised Note: It would be good if the options to provide additional technical metadata were based on either the digital file type expressed in the component surrogate record and / or the file extension in the file identification. That is, for a digital file type for image, the operator would only have the option to enter additional image technical metadata Add additional technical metadata for image files Operator selects option to extend technical metadata for image files Operator enters values for any of these elements: Mime type Byte order Compression scheme Color space At this time, there is no option to record additional technical metadata for audio and video files. Machine returns a template for additional technical metadata. Description Functional Area: Surrogates Page:94

96 Reference Black White Strip Offsets Rows per Strip Strip Byte Counts Planar Configuration Orientation Sampling Frequency Unit X Sampling Frequency Y Sampling Frequency Image Width Image Length Bits Per Sample Samples Per Pixel Source type Source ID Image Producer Image Device Type Scanner Manufacturer Scanner Model Name Scanning Software Scanning Software Version Number Processing software Save additional technical metadata Machine checks to assure that at least one field has values. If not, machine responds additional technical metadata cannot be saved. Otherwise, machine responds additional technical metadata is saved. Add additional technical metadata for text files Description Functional Area: Surrogates Operator selects option to extend technical metadata for image files Note: Should we have some stipulations about the data elements. For instance, we allow for the possibility to record Scanning software version number, without recording scanning software. A bit silly, eh? Machine returns a template for entering additional technical Page:95

97 Operator enters values for: Mime type Format metadata for text files Machine checks to assure that at least one field has values. If not, machine responds additional technical metadata cannot be saved. Otherwise, machine responds additional technical metadata is saved. Note: Since additional technical metadata is scant should we make it a requirement? Note: It may be possible to use a plug-in application, such as JHOVE, for supporting extraction and recording of additional technical metadata. There is for images, however, considerable additional technical metadata that JHOVE does not extract, e.g., scanning information, image production information, and information about the source item. D-3.13: Inputs Surrogate object number Surrogate type Surrogate object type Surrogate title Surrogate resource title Surrogate resource identifier Surrogate container 1 type Surrogate container 1 first container id Surrogate container 1 second container id Surrogate container 2 type Surrogate container 2 first container id Surrogate container 2 second container id Description Functional Area: Surrogates Page:96

98 Surrogate source date expression Surrogate source begin date Surrogate source end date Surrogate extent statement Surrogate dimension statement Surrogate predominant language identifier Surrogate descriptive notes Surrogate restrictions apply Surrogate component arrangement type Surrogate component part label Surrogate component part sequence Surrogate component title Surrogate component date expression Surrogate component begin date Surrogate component end date Surrogate component predominant language identifier Surrogate component descriptive notes Surrogate component file type Surrogate component file group Surrogate component file name Surrogate component file use label Surrogate component file format identification Surrogate component file size Surrogate component file checksum Surrogate component file checksum method Surrogate component file date of creation Surrogate component image file mime type Surrogate component image file byte order Surrogate component image file compression scheme Surrogate component image file color space Surrogate component image file reference black white Surrogate component image file strip offsets Surrogate component image file rows per strip Surrogate component image file strip byte counts Surrogate component image file planar configuration Surrogate component image file orientation Surrogate component image file sampling frequency unit Surrogate component image file X sampling frequency Surrogate component image file Y sampling frequency Surrogate component image file image width Surrogate component image file image length Description Functional Area: Surrogates Page:97

99 Surrogate component image file bits per sample Surrogate component image file samples per pixel Surrogate component image file source type Surrogate component image file source id Surrogate component image file image producer Surrogate component image file image device type Surrogate component image file manufacturer Surrogate component image file model name Surrogate component image file software Surrogate component image file software version number Surrogate component image file processing software Surrogate component text file mime type Surrogate component text file format Description Functional Area: Surrogates Page:98

100 D-3.14 Data Flow Diagram Description Functional Area: Surrogates Page:99

101 Description Functional Area: Surrogates Page:100

102 Description Functional Area: Surrogates Page:101

103 Description Functional Area: Surrogates Page:102

104 Description Functional Area: Surrogates Page:103

105 Description Functional Area: Surrogates Page:104

106 Description Functional Area: Surrogates Page:105

107 Description Functional Area: Surrogates Page:106

108 Description Functional Area: Surrogates Page:107

109 Description Functional Area: Surrogates Page:108

110 Description Functional Area: Surrogates Page:109

111 D-3.15 Screen Sequences Description Functional Area: Surrogates Page:110

112 Description Functional Area: Surrogates Page:111

113 Description Functional Area: Surrogates Page:112

114 Description Functional Area: Surrogates Page:113

115 Description Functional Area: Surrogates Page:114