The genre of the thing (music group, film, etc.)
RightsStatement (Value must be RightsStatement)
Access Rights may include information regarding access or restrictions based on privacy, security, or other policies.
Information about who can access the resource or an indication of its security status.
The distinction between titles and alternative titles is application-specific.
<dc:created rdf:label="sort date"/> <dc:created>%value%</dc:created>
Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty.
Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [ISO 8601-1] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [W3CDTF] or the Extended Date/Time Format Specification [EDTF]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing.
A point or period of time associated with an event in the lifecycle of the resource.
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Recommended practice is to specify the file size in megabytes and duration in ISO 8601 format.
Recommended practice is to use a controlled vocabulary where available. For example, for file formats one could use the list of Internet Media Types [MIME]. Examples of dimensions include size and duration.
The file format, physical medium, or dimensions of the resource.
Recommended practice is to identify the resource by means of a string conforming to an identification system. Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN). Persistent identifiers should be provided as HTTP URIs.
An unambiguous reference to the resource within a given context.
This property is intended to be used with non-literal values. This property is an inverse property of Has Part.
A related resource in which the described resource is physically or logically included.
Changes in version imply substantive changes in content rather than differences in format. This property is intended to be used with non-literal values. This property is an inverse property of Has Version.
A related resource of which the described resource is a version, edition, or adaptation.
Date of formal issuance of the resource.
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. Recommended practice is to refer to a rights statement with a URI. If this is not possible or feasible, a literal value (name, label, or short text) may be provided.
Information about rights held in and over the resource
This property is intended to be used with non-literal values. The described resource may be derived from the related resource in whole or in part. Best practice is to identify the related resource by means of a URI or a string conforming to a formal identification system.
A related resource from which the described resource is derived.
Spatial characteristics of the resource.
Recommended practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMI-TYPE]. To describe the file format, physical medium, or dimensions of the resource, use the property Format.
Date (often a range) of validity of a resource.
Identifies input methods that are sufficient to fully control the described resource
Subject must be ActionAccessSpecification, Demand, Offer
The beginning of the availability of the product or service included in the offer.
Subject must be AudioObject, ImageObject or VideoObject
The caption for this object. For downloadable machine formats (closed caption, subtitles etc.) use MediaObject and indicate the encodingFormat.
Subject must be CreativeWork or RsvpAction
CreativeWork (Subject must be CreativeWork)
The location depicted or described in the content. For example, the location in a photograph or painting.
A combination of date and time of day in the form [-]CCYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm] (see Chapter 5.4 of ISO 8601)
A relationship between an organization and a department of that organization, also described as an organization (allowing different urls, logos, opening hours). For example: a store with a pharmacy, or a bakery with a cafe.
Subject must be ContactPoint, Organization, or Person
In the U.S., the last name of a Person. this can be used along with givenName instead of the name property.
Size of the application / package (e.g. 18MB). In the absence of a unit (MB, KB etc.), KB will be assumed.
Genre of the creative work, broadcast channel or group.
Given Name. In the U.S., the first name of a Person. This can be used along with familyName instead of the name Property
An honorific suffix preceding a Person's name such as M.D./PhD/MSCSW
The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
A license document that applies to this content, typically indicated by URL.
The location where the CreativeWork was created, which may not be the same as the location depicted in the CreativeWork.
The result produced in the action. e.g. John wrote a book.
<rdf:Property rdf:about="http://schema.org/sameAs"> <rdfs:comment>URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.</rdfs:comment> <rdfs:label>sameAs</rdfs:label>
rdf:Property rdf:about="http://schema.org/sameAs" rdfs:label>sameA
URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.
CreativeWork, Event, Grant, MedicalStudy, Organization, Person
Subject must be from CreativeWork, Event, Grant, MedicalStudy,Organization or Person.
A person or organization that supports a thing through a pledge, promise, or financial contribution. e.g. a sponsor of a Medical Study or a corporate sponsor of an event.
Identifies the volume of publication or multi-part work; for example, "iii" or "2".
"If you have questions about permitted uses of this content, please contact the [ARMINDA administrator]"
"The author(s) chose to restrict access to this work to current Whitman students, faculty, and staff. Please log in to view it."
(Newspapers) The Whitman College Pioneer was a student-run newspaper that covered campus news, sports, arts, special events, and more. The Pioneer was published weekly during the academic year from 1896-2016. In 2016, the name of the paper was changed to the Whitman Wire.
As of 2/7/2020 the IMI is not in active use.
[If the IMI column is empty, I am ignoring the MODS assignment, and not crosswalking to RDF]
List of IMI that are of use in Harper Joy Collection
List of IMI that are of use in Maxey Collection
Proposed IMI sheet for new Archival Collections
Orbis Cascade Alliance Dublin Core Best Practices Guidelines
The purpose of the Orbis Cascade Alliance’s Dublin Core Best Practices Guidelines are to: ● ensure a basic level of uniformity in the structure, encoding, and content of Alliance digital object metadata in keeping with the Mountain West Digital Library Dublin Core metadata application profile and other relevant standards; ● promote interoperability within Alliance institutions metadata records developed from diverse repositories; and ● facilitate access to digital content by end users.
As of 3/10/20 no IMI sheet for Oral History. Treat no different than Archives Master Sheet
List of IMI that are of use in Oral History Collection
List of IMI that are of use in Sheehan Collection
displayLabel; shareable; altRepGroup; altFormat; contentType; xlink; lang; xml:lang; script; transliteration
Used to record a succinct summary of some aspect of the content of the resource. When creating a MODS record for a digital surrogate, record a summary of the content of the original resource. If only a portion of the resource was digitized, summarize only that portion. A link may be supplied in lieu of or in addition to the content. This element is repeatable.
MODS/abstract : A summary of the content of the resource. displayLabel – This attribute provides additional text associated with the element if needed for display purposes. The preferred text with its capitalization should be included, but not delimiters such as colons.
type; displayLabel; altRepGroup; altFormat; contentType; xlink; xml:lang; script; transliteration
One use of <accessCondition> is to indicate rights relating to access and use of a resource, particularly digital resources. The audience for such rights information is the end user, so rights information should be as free of legalese and technical jargon as possible. State clearly any restrictions on use of the resource, including explicitly mentioning lack of copyright restrictions when the resource is in the public domain. Also provide contact information for use by end users who wish to pursue required permissions for publication, exhibit, or other types of dissemination. A link may be supplied in lieu of or in addition to the content. If, for example, you maintain rights information relating to specific resources on a website, you may wish to provide a URL for that website in lieu of a textual rights statement. When doing so, you should provide enough textual explanation, along with the URL, to make the purpose of the URL clear to end users. This element is extensible to allow for using an established XML schema outside of MODS for the information, e.g. the CDL Copyright schema. When used in this manner, <accessCondition> becomes a container element.
Information about restrictions imposed on access to a resource.
<affiliation> may also contain other elements that are part of the affiliation, such as email address, street address, job title, etc.
The name of an organization, institution, etc. with which the entity recorded in <name> was associated at the time that the resource was created.
<copyInformation> is a container element. Data is entered in the subelements.
<subLocation> <shelfLocator> <electronicLocator> <note> <enumerationAndChronology> <itemIdentifier>
Information about a specific tangible instance of a bibliographic resource or set which comprises one or more pieces via indication of sublocation and/or locator.
encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration
The date may be in textual or structured form. If it is structured, the encoding attribute should specify the format. No good standard for encoding BCE dates in a structured form currently exists; until such time as these recommendations emerge, BCE dates may be represented in textual forms only. The MODS schema includes several date elements intended to record different events that may be important in the life of a resource. When multiple date elements apply but would contain identical data, institutions may choose to use only one of the relevant date elements. Mark one and only one date as a key date using keyDate="yes" attribute. When a date is uncertain or cataloger-supplied, indicate this through the use of the qualifier attribute rather than inserting characters such as "ca.", brackets, or a question mark as part of the date string. When only a decade is known, enter a date range for the entire decade and mark the date as questionable. When only a century is known, enter a date range for the entire century and mark the date as questionable.
Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource. The date that the resource was published, released, or issued.
type; encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration
See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components. <dateOther> may be used with the type attribute to designate a specific kind of date which was not deemed of sufficient general use to have its own date element.
A date that does not fall into another category but is important to record.
See <dateIssued> for the following information on recording dates: date structure, recording multiple dates, key date marking, and recording unknown date components. Specific DLF/Aquifer Guidelines
A date in which the content of a resource is valid.
xmlns:dc= "http://purl.org/dc/elements/1.1/"
type; level; lang; xml:lang; script; transliteration
Use this subelement to indicate the numbering and type of designation of the part in relation to the parent item.
Contains numbering and type of designation of the part in relation to the host/parent item in which a host item resides.
The <displayForm> element makes it possible to display personal names in direct order rather than inverted. For some applications, contractual agreements require that the form of the name provided on the resource be provided. If the display name is an entire statement of responsibility, <displayForm> may be indicated in a note (with type="statement of responsibility") along with any other text in the statement of responsibility and also repeated here if desired.
The unstructured form of the name as given on the resource.
type; authority; authorityURI; valueURI; lang; xml:lang; script; transliteration
Record the form of the digitized and analog original resources if such information will be useful. The element should be used to characterize the resource itself rather than the content of the resource, which would be <genre>. Either a controlled list of values or free text may be used. Specific DLF/Aquifer Guidelines The use of the type attribute is not recommended with by the DLF/Aquifer Implementation Guidelines for Shareable MODS Records due to the lack of controlled values, making it of limited usefulness for aggregators.
A designation of a particular physical presentation of a resource, including the physical form or medium of material for a resource.
authority; authorityURI; valueURI; lang; xml:lang; script; transliteration
Use to define the publication pattern of the item.
Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource. A statement of publication frequency in textual form.
authority; valueURI; authorityURI; lang; xml:lang; script; transliteration; altRepGroup; usage; displayLabel; type
contains terms that give more specificty for the form of an object than the broad terms used in typeOrResource. The terms may be from a controlled list with a designation of the autohritative list used i the authority attribute, or it may be an uncontrolled term. If no authority is specified, it is assumed that the term is uncontrolled.
A term or terms that designate a category characterizing a particular style, form, or content, such as artistic, musical, literary composition, etc.
If a controlled subject term is used, indicate authority using the authority attribute at the <subject> level. If the geographic name is part of a corporate body name (i.e., United States. Senate), it is coded with the <name> subelement, not <geographic>.
Used for geographic subject terms that are not appropriate for the <hierarchicalGeographic> element.
AAT, LCSH, COAR, Whitman College local genre list
LCSH, MeSH, Whitman College localized Subject list
See collection guidelines for creation protocols
Holdings information consists of copy-specific information about the resource, information about the specific location within an institution, version information, and other information that is peculiar to the institution. <holdingSimple> is a set of MODS internally defined elements and corresponds roughly to summary holdings information. If more granularity is required, <holdingExternal> may be used in lieu of <holdingSimple> with elements from an external schema. <holdingSimple> is a container element for the single subelement, <copyInformation> which has several subelements. <holdingSimple> is not repeatable; if additional holdings statements are needed for the resource, repeat <location> with appropriate subelements. For more information see MODS Holdings Information.
General information about what the institution identified in <physicalLocation> holds of the resource and its specific location.
type; displayLabel; invalid; altRepGroup; lang; xml:lang; script; transliteration; typeURI
<identifier> includes manifestation, expression, and work level identifiers. MODS makes a distinction between a persistent identifier of the resource and its electronic location. This element is used for the former; <location><url> is used for the latter. Repeat the <identifier> element for each applicable identifier recorded, including invalid and canceled identifiers.
Contains a unique standard number or code that distinctively identifies a resource.
<issuance> may be used with the following values: monographic – A resource that is either complete in one part or intended to be completed in a finite number of separate parts. Alternatively, more specific values distinguishing "single unit" from "multipart monograph" may be used. single unit – A type of monographic resource that is issued either as a single physical unit (e.g., as a single-volume monograph) or, in the case of an intangible resource, as a single logical unit (e.g., as a PDF file mounted on the Web). multipart monograph – A type of monographic resource issued in two or more parts (either simultaneously or successively) that is complete or intended to be completed within a finite number of parts (e.g., a dictionary in two volumes or three audiocassettes issued as a set). continuing – A resource that is issued over time with no predetermined conclusion. Continuing resources include serials and ongoing integrating resources, i.e. those that are continuously updated. Alternatively, more specific values distinguishing "serial" from "integrating resource" may be used. serial – A type of continuing resource issued in successive parts, usually bearing numbering, that has no predetermined conclusion (e.g., a periodical, a monographic series, or a newspaper). Includes resources that exhibit characteristics of serials, such as successive issues, numbering, and frequency, but whose duration is limited (e.g., newsletters of events) and reproductions of serials. integrating resource – A type of continuing resource that is added to or changed by means of updates that do not remain discrete and are integrated into the whole. An integrating resource may be tangible (e.g., a loose-leaf manual that is updated by means of replacement pages) or intangible (e.g., a Web site that is updated either continuously or on a cyclical basis). Collection, which designates an aggregation level, is included in the collection attribute in the <typeOfResource> element
Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource. The date on which the resource was digitized or a subsequent snapshot was taken.
usage; objectPart; displayLabel; altRepGroup; lang; xml:lang; script; transliteration
<language> is a container element; the actual language values are recorded in the subelement <languageTerm>. If the content of the resource is in more than one language, the objectPart attribute for <language> is used and the <language> element is repeated. <language> may also be expressed in conjunction with each element in a MODS encoding by means of the xml:lang and/or lang attributes to designate the language used in the metadata value; see the section on language in Attributes Used Throughout the MODS Schema for more information. The subelement <languageOfCataloging> under <recordInfo> is used to give the language of the metadata in the record as a whole. It designates the language of the metadata record, while this <language> element designates the language of the resource.
A designation of the language in which the content of a resource is expressed.
If expressed in coded form, the source of the code is contained in the value of the authority attribute. If no authority is given, it is assumed that the content is textual. If there is more than one representation of the same language, e.g. using different forms of the same language (code or text) or from different authorities, <languageTerm> is repeated within the <language> container.
Contains the textual or coded form for the language of the content of the resource.
displayLabel; altRepGroup; lang; xml:lang; script; transliteration
<location> is a container element; specific data is recorded in the subelements.
<shelfLocator> <url> <holdingSimple> <holdingExternal>
Identifies the institution or repository holding the resource, or the electronic location in the form of a URL where it is available.
type; authority; authorityURI; valueURI; usage; displayLabel; nameTitleGroup; altRepGroup; xlink; ID; lang; xml:lang; script; transliteration; etal
<name> is a container element that contains all subelements related to name information. Role values are used to indicate the particular relationship between the name and the resource. Some implementors have used the <role> subelement with the value "creator". to retain the concept of main entry. In addition to describing creators, <name> is used as a subelement of <subject>. For names used as subjects, see the <subject> section of the guidelines. A name may be linked to a uniform title in the record using the nameTitleGroup attribute. A name may be designated as the citation or "main" entry name using the usage attribute.
The name of a person, organization, or event (conference, meeting, etc.) associated in some way with the resource.
type; lang; xml:lang; script; transliteration
The name itself is always contained in a <namePart> element. MODS allows for either breaking up parts of the name (given and family, for example) in different <namePart> elements or enclosing the entire name in one element. Use of the former method affords more control in sorting and display and should be used if the data is readily available. Either method is acceptable. For greater interoperability, name elements should appear in the same order as in their authorized form (the authority cited in the <name> authority attribute). If no authority is used for personal names, last name or family name should appear first, followed by a comma, followed by first or given names. Parsing can be used to indicate a date associated with the name, to parse the parts of a corporate name, or to parse parts of a personal name if desired.
The name of a person, organization, or event (conference, meeting, etc) associated in some way with the resource -- The individual parsed parts that together make up the full name -- Designates the relationship (role) of the entity recorded in name to the resource described in the record
The individual parsed parts that together make up the full name.
[as of 2/7/20 there is no IMI column for these MODs fields] [If the there is no IMI column, I am ignoring the MODS assignment, and not crosswalking to RDF]
IMI fields with either no MODS mapping or contain empty content in IMI
RDF mapping not finished / no mapping to RDF
type; displayLabel; altRepGroup; xlink; ID; lang; xml:lang; script; transliteration; typeURI
General textual information relating to a resource.
Numbering can be sequencing in any form, e.g., Part 1, Supplement A, Book two.
Contains the actual number within the part.
eventType; displayLabel; altRepGroup; lang; xml:lang; script; transliteration
<originInfo> is a container element that contains all subelements related to publication and origination information. It includes all dates associated with the creation, issuance, and/or publication of the resource. Dates associated with the temporal content of the resource go under <subject>, and dates associated with the metadata go in <recordInfo>. Data is input only within each subelement.
Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource.
type; order; displayLabel; altRepGroup; ID; lang; xml:lang; script; transliteration
<part> is a container element used to provide detailed coding for physical parts of a resource. It may be used as a top level element to designate physical parts or under <relatedItem> for specifying the location of a part within a host/parent item. Use <part> when the MODS record in question refers to either a physical or structural part of a resource, rather than an intellectual part. To indicate part names and numbers that are subordinate to the title as distinct intellectual items, use with <partName> and/or <partNumber>. A newspaper issue is generally indicated in MODS with <part>, rather than indicating the issue number as part of the title. The <part> element at the top level is also used to describe one reel of microfilm in a set, or in any other case in which the part being described is not an intellectual whole by itself. When in doubt and only part numbers or names are needed, use <titleInfo> <partNumber> and/or <titleInfo> <partName>. When there is a separate intellectual entity with its own identity that is part of a larger work, use <relatedItem type="host"><part> to show the location of the part within that host item.
The designation of physical parts of a resource in a detailed form.
displayLabel; altRepGroup; lang; xml:lang; script; transliteration; unit
<physicalDescription> is a container element that contains all subelements relating to physical description information of the resource. Data is input only within each subelement. It is usually not necessary to include a full <physicalDescription> for every version of a resource known to exist; choose carefully which versions and elements are important. The examples given in these guidelines represent a sample of the types of data which may be important to expose. Repeating this element is not recommended.
<reformattingQuality> <internetMediaType> <extent> <digitalOrigin> <note>
Describes the physical attributes of the information resource.
type; authority; authorityURI; valueURI; displayLabel; xlink; lang; xml:lang; script; transliteration
<physicalLocation> typically includes specific information used to locate a resource within a collection, such as the name or code of an institution/repository, and perhaps subcollection. A shelf number is given in <shelfLocator>. <physicalLocation> may be expressed as text and/or as a code. Use the authority attribute to designate the source of the code. The attribute xlink may be used to link to additional information about the entity recorded in <physicalLocation>, e.g. the institution's website.
The institution or repository that holds the resource or where it is available.
<place> is a container element for <placeTerm> to indicate place of publication/origin. <place> is used in connection with the origin of a resource, i.e., creation, publication, issuance, etc. The <place> element should be omitted if no information about the originating place of the resource is known. Descriptive standards such as AACR2 may be used to determine which places to record for published resources. If a place of origin is known for an unpublished resource, it should also be recorded in <place><placeTerm>. Places as subjects are included under <subject><geographic> or <subject><hierarchicalGeographic>. Repeat <place> for recording multiple places.
Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource.
If both a code and a term are given that represent the same place, use one <place> and multiple occurrences of <placeTerm>. If different places, repeat <place><placeTerm>
Used to express place in a textual or coded form.
supplied; lang; xml:lang; script; transliteration
Record in <publisher> a named entity determined to be the publisher/originator for a resource or a statement about publication/origin. Descriptive standards such as AACR2 may be used to format the name of the publisher.
The name of the entity that published, printed, distributed, released, issued, or produced the resource.
This information can be useful to trace the provenance of a particular metadata record. The name or code should be pulled from an authoritative list and indicated in the authority attribute. <recordContentSource> should be repeated for each code or name recorded.
The code or name of the organization that either created or modified the original record.
If a structured date is used, indicate the formatting source using the encoding attribute.
The date or date and time on which the original MODS record was first created.
<recordInfo> is a container element that includes subelements relating to information necessary for managing metadata. This type of administrative information can help establish the provenance of a metadata record and may enable better interpretation of the content of the record. <recordInfo> may also include information that is relevant only to the creating or managing institution. <recordInfo> is not repeatable.
< recordContentSource> < recordCreationDate> < recordChangeDate> < recordIdentifier> < recordOrigin> < recordInfoNote> < languageOfCataloging> <descriptionStandard>
Use this subelement to record information about the origin, or provenance of the MODS record including what methods were used to prepare the MODS record (machine generated or human prepared) and what transformations have been applied (e.g., the result of converting an existing MARC 21 record to MARCXML and to MODS). <recordOrigin> can be free text or an institution may establish locally-controlled values for machine processing and consistency.
Shows the origin or provenance of the MODS record.
madsrdf:MADSScheme rdf:about="http://id.loc.gov/vocabulary/relators"
<role> is a container element for the role recorded in one or more <roleTerm> subelements. If there are different roles, repeat <role><roleTerm> as needed.
Designates the relationship (role) of the entity recorded in name to the resource describedin the record.
An authority attribute should be indicated if the role is in coded form or in textual form from a controlled term list. The Library of Congress maintains a list of sources for codes and terms, Relator and Role Code and Term Source Codes, and a relator code and term value list, MARC Code list for Relators. If both a code and a term are given that represent the same role, use one <role> and multiple occurrences of <roleTerm>. If different roles are given, repeat <role><roleTerm>.
Contains the textual or coded form of a relator/role.
<subLocation> may be repeated for multiple equivalent items in different sublocations within the institution named in <physicalLocation>.
Department, division, or section of an institution holding a copy of the resource.
authority; authorityURI; valueURI; usage; displayLabel; altRepGroup; xlink; ID; lang; xml:lang; script; transliteration
<subject> is a container element that contains subelements relating to the subject aspect of the resource. ' If the subject is a controlled heading from an authoritative list, use the authority attribute to indicate which authority was used. If no authority attribute is present, the data is assumed to be an uncontrolled term. If it is not desired to parse the subject subelements, use <subject><topic> and a string. Repeat <subject> for each subject string.
<geographic> <temporal> <titleInfo> <name> <genre> <hierarchicalGeographic> <cartographics> <geographicCode> <occupation>
A term or phrase representing the primary topic(s) on which a work is focused.
type; displayLabel; xlink: lang; xml:lang; script; transliteration
Use this subelement to record information in textual form when other subelements will not capture the appropriate information.
Contains unparsed information in textual form about the part.
Each element should follow the subelement for which it is appropriate (e.g., a part name or number may follow the title or the subtitle depending upon the situation). <namePart> subelement includes all parts of a title not covered by the other subelements of <titleInfo>. Dates may be recorded here only if considered part of the title (e.g., a date in a uniform title). (Publication dates are included under <originInfo>.) For parallel titles (i.e., equivalent titles in different languages), use separate <titleInfo> elements with type attribute equal to "translated" for each parallel title. For non-collective titles by the same author (i.e., separate titles with no inclusive title for the collection), use separate <titleInfo> elements with no type attribute.
A word, phrase, character, or group of characters that constitutes the chief title of a resource, i.e., the title normally used when citing the resource.
type; authority; authorityURI, valueURI; usage; displayLabel; supplied; nameTitleGroup; altRepGroup; altFormat; contentType; xlink; ID; lang; xml:lang; script; transliteration; otherType
Titles are an extremely important access point for digital library resources and are frequently used in brief record displays to assist end users in deciding whether to investigate a resource further. In supplying a title, consider expectations of end users for naming of resources. Choice and format of titles should be governed by a content standard such as the Anglo-American Cataloging Rules, 2nd edition (AACR2), Cataloguing Cultural Objects (CCO), or Describing Archives: A Content Standard (DACS). Details such as capitalization, choosing among the forms of titles presented on an item, and use of abbreviations should be determined based on the rules in a content standard. One standard should be chosen and used consistently for all records in a set. <titleInfo> is a container element that contains all subelements related to title information. Data content is contained in subelements. Do not include punctuation intended to delineate parts of titles that are separated into subelements of <titleInfo>. If multiple titles are recorded, repeat <titleInfo> for each. <titleInfo> is also repeated for each type attribute value. The language of the title may be indicated if desired using the xml:lang or lang attributes. A uniform title may be linked to a name in the record using the nameTileGroup attribute.
<subTitle> <partNumber> <partName> <nonSort>
A word, phrase, character, or group of characters, normally appearing in a resource, that names it or the work contained in it.
If the type of subject string is unknown, <topic> is used (since <subject> is a container element). If a controlled subject term is used, indicate authority using the authority attribute at the <subject> level.
Used as the tag for any topical subjects that are not appropriate in the <geographic>, <temporal>, <titleInfo>, <name>, <genre>, <hierarchicalGeographic>, or <occupation> subelements.
For example, use "5" to indicate a total of five pages.
Contains the total number of units within a part, rather than specific units.
collection; manuscript; usage; displayLabel; altRepGroup
Information in <typeOfResource> is about the original item. For example, in the case of a digitized photograph, <typeOfResource> would apply to the analog original; in born-digital materials, it would apply to the original digital format. This element includes a high-level type that categorizes the material in a general way using an enumerated list of values. More specific typing is done in the <genre> element. The attributes collection and manuscript are associated with a specific value used in <typeOfResource>. For example, a MODS object that consists of a collection of maps with associated text would be represented by two instances of <typeOfResource>. The first would be "cartographic" with attribute collection="yes", and the second would be "text" (with no attribute).
text – Resources that are basically textual in nature. cartographic – Includes maps, atlases, globes, digital maps, and other cartographic items. notated music – Graphic, non-realized representations of musical works, both in printed and digitized manifestations that represent the four components of musical sound: pitch, duration, timbre, and loudness. sound recording – Used when a mixture of musical and nonmusical sound recordings occurs in a resource or when a user does not want to or cannot make a distinction between musical and nonmusical. sound recording-musical – Used when a resource is predominately a musical sound recording. sound recording-nonmusical – Used when the sound recording is nonmusical in nature. still image – Includes two-dimensional images and slides and transparencies. moving image – Includes motion pictures and videorecordings, as well as television programs, digital video, and animated computer graphics—but not slides and transparencies. It does not include moving images that are primarily computer programs, such as computer games or computer-oriented multimedia; these are included in "software, multimedia". three dimensional object – Includes man-made objects such as models, sculptures, clothing, and toys, as well as naturally occurring objects such as specimens mounted for viewing. software, multimedia – Appropriate for any electronic resource without a significant aspect that indicates one of the other <typeOfResource> categories. It includes: software, numeric data, computer-oriented multimedia, and online systems and services. mixed material – Indicates that there are significant materials in two or more forms that are usually related by virtue of their having been accumulated by or about a person or body. Mixed material includes archival fonds and manuscript collections of mixed forms of materials, such as text, photographs, and sound recordings.
A term that specifies the characteristics and general type of content of the resource.
displayLabel; dateLastAccessed; note; access; usage
<url> is for an electronic location from which the resource is available. Note that <identifier> is used for persistent identifiers that may or may not be resolvable.
Contains the Uniform Resource Location of the resource.
Resource reflecting an individual, material embodiment of a Work
Resource reflecting a conceptual essence of a cataloging resource.
List of IMI that are of use in Archives Collections
As of 3/11/20 IMI sheets for newspapers are under construction. Leave alone until further notice.
List of IMI that are of use in Newspaper Collection
[Instances assigned to NewspaperCollection are a combination of both an IMI test sheet AND the twig template. Information may be duplicated as it's unclear where information comes from as of 2/20/20]
List of IMI that are of use in Scholarship Collections
[as of 2/13/20 Scholarship Collection will have MODS/genre in place of document_type. A new IMI column will be made, one which is separate from newspapers MODS/genre]
List of IMI that are of use in Theses Collection
[Subjects - broken out into topic, person, location is doable]
/mods/abstract /mods/abstract/@displayLabel="Abstract"
A summary of the resource, primarily used with scholarship objects
/mods/accessCondition /mods/accessCondition/@type="Access Statement"
Field that indicates item may be accessed by only current Whitman affiliates (netID holders).
Content moved to IMI/source. Removed from all collections.
/mods/name/namePart /mods/name/@displayLabel="Advisors"
“A person under whose supervision a student develops and/or presents an academic paper or project, including theses and capstone projects.”
Possibly required for module. Ideally remove
Box in which newspapers live in the Archives.
BePress inherited field which indicated the collection --bucket-- an item is associated with
Added to MODS through Newspaper-specific TWIG Possibly required for module. Ideally remove
Necessary for Islandora 7. Unsure of its role in Islandora 8
Tells what content model the file is -- audio, image.etc; tells what type of file for Islandora to expect.
Content moved to IMI/abstract. Removed from all collections
identifies the entity or entities that made contributions to the creation of the resource but whose contributions are secondary to any person or organization specified in the creator(s) field.
Content moved to IMI/contributor. Removed from all collections
(S.A.T) identifies the entity/entities primarily responsible for making the resource (Sheehan) Person(s) and accompanying note associated with creation of item,
Date of creation or publication of original object in human readable format for public viewing
Encoded date of creation or publication of the original object with qualifiers and date ranges when applicable
/mods/originInfo/dateIssued /mods/originInfo/@displayLabel="Date Issued"
Encoded date of creation or publication of the original object that strips out qualifiers and date ranges to allow us to sort on date in ARMINDA
College division in which the item is categorized
/mods/abstract /mods/abstract/@displayLabel="Description"
An account of the resource, primarily used for archival objects
Content moved to IMI/provenance. Removed from all collections
Content moved to IMI/extent. Removed from all collections
Date of which item is released for public viewing.
Statement of the physical size or duration of the object, such as dimensions, number of items, pages, or running time.
Used in ARMIDNA as the filename of object; often times includes in ingest path for field - filename is in path
Content moved to IMI/genre. Removed from all collections.
Indicates institution or program that helped to fund research project
/mods/genre /mods/genre/@authority="lctgm"
A more detailed sub-type refining the broader Work Type element; provides a specific characterization of the nature or style of the original content source
Character string or number that clearly and uniquely identifies a digital object or resource. This field ensures that individual digital objects can be accessed, managed, stored, recalled, and used reliably.
Content moved to IMI/collection_name. Removed from all collections.
Content moved to IMI/author or IMI/contributor. Removed from all collections
Indicate issue number sequential order of volume
Character string or number that clearly and uniquely identifies a digital object or resource. This field ensures that individual digital objects can be accessed, managed, stored, recalled, and used reliably specifically for newspapers
Newspapers indicate language of content, including English language
the non-English language of the source content being described : applies to textual or spoken word (linguistic) content).
Content moved to IMI/keywords. Removed from all collections.
Does not get transformed into MODS. Temporary location for information used for item ingest into ARMINDA
This does not have a purpose unless there are compound objects. Once items have PIDS, this is moot.
The line_number is the CSV line number that the IMI module needs in order to keep the CSV in order.
Content moved to IMI/extract. Removed from all collections
Tells where the file is when item is uploaded to Islandora
Provides place names associated with the creation or issuance of a resource.
Possibly required for newspaper module. Ideally move to IMI/extent
Tells Islandora 7l the hierarchy of where an object lives
/mods/identifier /mods/identifier/@displayLabel="Permanent URL"
Persistent Identifier That is generated sequentially.
Content moved to IMI/keyword. Removed from all collections
/mods/abstract /mods/abstract/@displayLabel="Production Info"
Content removed from all collections, but kept in separate Archives documents.
Content moved from IMI/mods_date_created_keydate,IMI/mods_display_date, and IMI/oai_harvester_date. Removed from all collections
"Content moved to IMI/contributor. Removed from all collections
Contains provenance information about the object: [currently] donor information and/or when and how the object was acquired by Whitman College.
Possibly required for newspaper module. Ideally moved to IMI/mods_date_created_keydate, IMI/mods_display_date, IMI/oai_harvester_date
Encoded date of creation or publication of the original object for newspapers
the name of the entity that published, printed, distributed, released, issued, or produced the resource. This may be a formal publisher, or for unpublished materials, a university department or other corporate entity.
/mods/accessCondition /mods/accessCondition/@displayLabel="Access Statement"
HTML link to ARMINDA page linking to contact information for use by end users who wish to pursue required permissions for publication, dissemination, etc
/mods/accessCondition /mods/accessCondition/@displayLabel="Rights Statement"
URL that indicates copyright and/or creative commons status. Can include free-text explanation of rights.
Row number for newspapers, required for newspaper module.
Sequential number for newspapers, required for newspaper module.
Term(s) representing the primary topic(s) on which a work is focused
Content moved to IMI/rights. Removed from all collections
Name given to the resource or supplied title if one is absent
An alternative title of the described resource including abbreviations and translations
Content moved to IMI/work_type. Removed from all collections
URL linking file content not hosted in ARMINDA to metadata record, in ARMINDA
Basic conceptual indication of the kind of object being described, using broad terms.
Year author graduated from Whitman College
If you have questions about permitted uses of this content, please contact the ARMINDA administrator.
<originInfo displayLabel="Broad Date %value %
<originInfo displayLabel="Broad Date> %value %
The Whitman College Pioneer was a student-run newspaper that covered campus news, sports, arts, special events, and more. The Pioneer was published weekly during the academic year from 1896-2016. In 2016, the name of the paper was changed to the Whitman Wire.
<originInfo displayLabel="Embargo Period"> <dateValid>%value%</dateValid>
<originInfo displayLabel="Embargo Period"> <dateValid encoding="edtf">%value%</dateValid>
<originInfo displayLabel="Embargo Period"> <dateValid encoding="w3cdtf">%value%</dateValid>
[possibly old twig mapping -- information not reflected in RDF Crosswalk spreadsheet]
<originInfo displayLabel="Graduation Year"> <dateOther type="graduation_year">%value%</dateOther>
<originInfo displayLabel="Graduation Year"> <dateOther type="graduation_year" encoding="marc">%value%</dateOther>
<originInfo displayLabel="Publication Date"> <dateOther type="publication_date" qualifier="approximate">%value</dateOther>
<originInfo displayLabel="Publication Date"> <dateOther type="publication_date" encoding="w3cdtf">%value</dateOther>
%value% %value% %value% %value% %value% Creator(s)
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created">%value</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" point="start">%value%</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" point="end">value%</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" qualifier="approximate">value%</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" qualifier="approximate" point="end">value%</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" qualifier="approximate" point="start">value%</dateOther>
<originInfo displayLabel="Date Created (circa)"> <dateOther type="date_created" qualifier="approximate" encoding="marc">value%</dateOther>
For multiple contributors, either repeat the property or separate values with a semicolon. Form according to RDA. When adding a contributor role use terms listed in RDA Relationship Designators for Contributors or the MARC code List for Relators. The role should be preceded by a comma and one space.
Relationship Designators to Relate Persons to Other Persons Record an appropriate term from the following list with the authorized access point or identifier for a related person (see 30.1). Apply the general guidelines on using relationship designators at K.1. alternate identity: A pseudonymous or other identity assumed by a person. Reciprocal relationship: real identity. colleague: A fellow member of a profession, staff, or academic faculty. Reciprocal relationship: colleague. assistant: A colleague who helps another person. Reciprocal relationship: assistant to. assistant to: A colleague who is helped by another person. Reciprocal relationship: assistant. co-worker: A colleague who works with or shares a task with another person. Reciprocal relationship: co-worker. partner: A colleague working with another person in an activity of common interest, most often, a business partnership. Reciprocal relationship: partner. fellow student: An associate of another student who is also formally engaged in learning. Reciprocal relationship: fellow student. friend: A person who shares a bond of mutual affection or regard with another person. Reciprocal relationship: friend. real identity: A real person who assumes an alternate identity. Reciprocal relationship: alternate identity. student: A person who receives instruction from another person. Reciprocal relationship: teacher. teacher: A person who instructs another person. Reciprocal relationship: student.
"An entity responsible for making contributions to the resource"
19.2 -- If there is more than one creator responsible for the work, only the creator having principal responsibility named first in manifestations embodying the work or in reference sources is required. If principal responsibility is not indicated, only the first-named creator is required. (http://access.rdatoolkit.org/rdachp19_rda19-395.html)
For multiple creators, either repeat the property or separate values with a semicolon. When present, form according to RDA
"An entity primarily responsible for making the resource"
A resource may have several dates associated with it. The date covered by this table refers to the creation of the original resource, that is, when the resource was first created, before undergoing any conversions. Additional dates are allowed, though only the first date will be harvested. If the date is unknown, specify an estimated date or date range.
Yes, but only the first dc:date will be harvested
"A point or period of time associated with an event in the lifecycle of the resource"
"Anything significant about the digital resource not covered elsewhere. Use standard puncuation and grammar to describe item's history, physical apperance, contents, abstact, etc"
"Use for the digital format of the resource, form as an IMT term. For multiple formats, either repeat the property or separate values with a semicolon.
"The digital file format of the resource"
"Use for the resource identifier. Many digital asset management systems automatically create, populate, and map the main identifier field. Thi smain identifier is a url for the resource. Additional identifier fields may be created as needed for local use, such as call number, filename, etc. However only the identifier containing the uri leading back to the resource will be harvested. If two uris are present, and one is a doi, the doi will be harvested.
Yes, but only the record uri will be harvested
"An unambiguous reference to the resource within a given context"
"Use for ISO639-2 three letter codes or language names as they appear in ISO 639-2. For multiple languages, either repeat the property or separate values with a semicolon. If there is no linguistic content, leave blank."
"For the relation value as aN Archives West ARK. Additional relation fields/values may be created as needed for local use, to show relationsihps between the resources and other resources. However, only the relation value containing the Archives West ARK will be harvested"
yes, but only the Archives West Resource Key will be harvested.
URI, rightsstatements.org, creativecommons.org
"Use a pair of rights statements to describe the copyright status of the resource. Do not use rights to describe property or privacy rights.
yes, rights is required as exactly 2 separate properties
"Information about the copyright of the resource"
"Use when the resource is th eresult of digitization of non-digital originals. In these cases, sufficient information to identify and find the original resource is provided."
"A related resource from which the described resource is derived"
"Use for spatial coverage only. For multiple coverage statements, either repeat the property or separate values with a semicolon. Use for human readable place name or geographic coordinates.
"The spatial topic of the resource, the spatial applicibility of the resource, or the jurisdiction under which the resource is relevant"
"Use for all subjects. For multiple subject, either repeat the property, or separate values with a semicolon.
"Each title property should have a single title value. For mulitple titles, repeat the property. Only one title will be harvested as a title (the first). All subsequent title properties will be harvested as alternative titles"
"Use to describe the type of resource with at least one value from DCMI Type vocabulary."
Class: Summary (Description of the content of a resource, such as an abstract, summary, etc.)
Summary or abstract of the resource described.
Applies to special cases for Sheehan Gallery Collection
madsrdf:Identifier (Value must be from Class: Identifier (A madsrdf:Identifier resource describes an identifier by associating the identifier value with its type. To be used to record identifiers for a resource in the absence of URIs.))
Associates a resource with a madsrdf:Identifier.
Contains the measured units making up the part.
supplied; unit; lang; xml:lang; script; transliteration
<extent> may be used with electronic resources, e.g. for digitized collection of slides, to show how many slides constitute the resource.
A statement of the number and specific material of the units of the resource that express physical extent.
Relates an item to a place that is associated with an item
"Relates a resource to an appellation of resource that consists of a code, number, or other string, usually independent of natural language and social naming conventions, used to identify a resource."
"Relates a resource to a designation in the form of numbers or alphabetic characters, or a date or other timespan, that is used to indicate a sequence of a part resource within a whole resource."
"Relates a resource to a formal recognition of excellence, etc., given by an award- or prize-granting body, for the content of a resource."
"Relates a resource to a group with which an agent is affiliated or is affiliated through employment, membership, cultural identity, etc."
Relates a resource to a larger resource of which a part is a discrete component.
"Relates a resource to a note on resource that provides information on the production of a resource."
<?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xml:base="http://rdaregistry.info/Elements/u/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"> <rdf:Description rdf:about="http://rdaregistry.info/Elements/u/P60101"> <rdfs:label xml:lang="en">is translation of</rdfs:label> </rdf:Description> </rdf:RDF>
rdfs:label xml:lang="en">is translation of
"Relates a resource to a resource that is translated, i.e., the text expressed in a language different from that of an original resource."
"Relates a resource to a resource that provides a guide to the organization, arrangement, and contents of an archival collection."
Property of has sequential resource relationship with
Relates a resource to a resource whose chronological coverage is after that of another resource.
"Relates a resource to a significant date associated with the history of an agent, or the date or range of dates on which a conference, etc., was held, or a date with which an agent is otherwise associated."
<reg:p60332 >productionStatement</reg:p60332>
"Relates a resource to a statement identifying a place or places of production, producer or producers, and date or dates of production of an unpublished resource."
"Relates a resource to a system of arranging materials in an archival resource or a collection."
<reg:p60487>{{jsonize(cells["filepath"].value).replace('null', '')}}</reg:p60487>
"Relates a resource to an indication of content that provides alternative sensory modes to perceive a primary content of a resource."
"Relates a resource to limitations placed on access to a resource."
"Relates a resource to an other title information in a language or script that differs from that recorded in an other title information element."
Property/Resource (of has date of resource)
"Relates a resource to a timespan during which an academic degree is conferred by a granting institution or faculty."
"Relates a resource to a place from which a resource originated."
"Relates a resource to a date or range of dates on which a conference, congress, meeting, exhibition, fair, festival, etc., was held."
Relates a resource to a type, number, and measurement unit that quantify an aspect of the extent of a resource."
"has immediate source of acquisition of resource"
"Relates a resource to the circumstances under which an item is directly acquired, including a method, source, and date of acquisition."
"Relates a resource to a note on resource that provides information associated with the recording, filming, etc., of the content of a resource."
"Relates an entity to an appellation of entity that consists of a code, number, or other string, usually independent of natural language and social naming conventions, used to identify an entity.
Property of "has related resource of timespan"
rdfs:isDefinedBy rdf:resource="http://rdaregistry.info/Elements/u/" / reg:status rdf:resource="http://metadataregistry.org/uri/RegStatus/1001" / rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property" / rdfs:label xml:lang="en">is date of resource of
Relates a timespan to a resource associated with an earliest timespan.
"Relates a timespan to an entity that is associated with a timespan."
A person, family, or organization that designs the costumes for a moving image production or for a musical or dramatic presentation or entertainment
An author of a screenplay, script, or scene
A person, family, or organization responsible for creating a work that is primarily textual in content, regardless of media type (e.g., printed text, spoken word, electronic text, tactile text) or genre (e.g., poems, novels, screenplays, blogs). Use also for persons, etc., creating a new work by paraphrasing, rewriting, or adapting works by another creator such that the modification has substantially changed the nature and content of the original or changed the medium of expression
A person or organization relevant to a resource, who is engages specifically to provide an intellectual overview of a strategic or operational task and by analysis, specification, or instruction, to create or propose a cost-effective course of action or solution
A person, family or organization responsible for making contributions to the resource. This includes those whose work has been contributed to a larger work, such as an anthology, serial publication, or other compilation of individual works. If a more specific role is available, prefer that, e.g. editor, compiler, illustrator
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <madsrdf:MADSScheme rdf:about="http://id.loc.gov/vocabulary/relators" xmlns:madsrdf="http://www.loc.gov/mads/rdf/v1#"> <madsrdf:hasMADSSchemeMember> <madsrdf:Authority rdf:about="http://id.loc.gov/vocabulary/relators/dgs"> <madsrdf:authoritativeLabel>Degree supervisor</madsrdf:authoritativeLabel> </madsrdf:Authority> </madsrdf:hasMADSSchemeMember> </madsrdf:MADSScheme> </rdf:RDF>
madsrdf:hasMADSSchemeMember madsrdf:Authority rdf:about="http://id.loc.gov/vocabulary/relators/dgs" madsrdf:authoritativeLabel>Degree supervisor
(Scholarship) A person overseeing a higher level academic degree
A former owner of an item who donated that item to another owner
A person responsible for the general management and supervision of a filmed performance, a radio or television program, etc.
A person, family, or organization contributing to a resource by revising or elucidating the content, e.g., adding an introduction, notes, or other critical matter. An editor may also prepare a resource for production, publication, or distribution. For major revisions, adaptations, etc., that substantially change the nature and content of the original work, resulting in a new work, see author
A person or organization who designs the lighting scheme for a theatrical presentation, entertainment, motion picture, etc.
A person or organization responsible for publishing, releasing, or issuing a resource
A person or organization associated with the production (props, lighting, special effects, etc.) of a musical or dramatic presentation or entertainment
A person who produces and reproduces the sound score (both live and recorded), the installation of microphones, the setting of sound levels, and the coordination of sources of sound for a production
A person, family, or organization sponsoring some aspect of a resource, e.g., funding research, sponsoring an event
A person who translates the rough sketches of the art director into actual architectural structures for a theatrical presentation, entertainment, motion picture, etc. Set designers draw the detailed guides and specifications for building the set
A person who is in charge of everything that occurs on a performance stage, and who acts as chief of all crews and assistant to a director during rehearsals
A person who is ultimately in charge of scenery, props, lights and sound for a production
A performer contributing to a resource by giving instruction or providing a demonstration
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <madsrdf:MADSScheme rdf:about="http://id.loc.gov/vocabulary/relators" xmlns:madsrdf="http://www.loc.gov/mads/rdf/v1#"> <madsrdf:hasMADSSchemeMember> <madsrdf:Authority rdf:about="http://id.loc.gov/vocabulary/relators/ths"> <madsrdf:authoritativeLabel>Thesis advisor</madsrdf:authoritativeLabel> </madsrdf:Authority> </madsrdf:hasMADSSchemeMember> </madsrdf:MADSScheme> </rdf:RDF>
madsrdf:hasMADSSchemeMember madsrdf:Authority rdf:about="http://id.loc.gov/vocabulary/relators/ths" madsrdf:authoritativeLabel>Thesis advisor
A person under whose supervision a degree candidate develops and presents a thesis, mémoire, or text of a dissertation
This term is proposed for full integration into Schema.org, pending implementation feedback and adoption from applications and websites.
period during which access to academic journals is not allowed to users who have not paid for access
The familyName property is provided (alongside givenName) for use when describing parts of people's names. Although these concepts do not capture the full range of personal naming styles found world-wide, they are commonly used and have some value.
The firstName property is provided (alongside lastName) as a mechanism to support legacy data that cannot be easily interpreted in terms of the (otherwise preferred) familyName and givenName properties. The concepts of 'first' and 'last' names do not work well across cultural and linguistic boundaries; however they are widely used in addressbooks and databases.
An organization funding a project or person.
The givenName property is provided (alongside familyName) for use when describing parts of people's names. Although these concepts do not capture the full range of personal naming styles found world-wide, they are commonly used and have some value
<foaf:agent> <foaf:person> <foaf:firstName>%value%</foaf:firstName> <foaf:givenName>%value%</foaf:givenName> <foaf:familyName>%value%</foaf:familyName> <bibo:suffix>%value%</bibo:suffix> <madsrdf:aut>{firstName} {givenName} {familyName} {suffix}</madsrdf:aut> </foaf:person> </foaf:agent>