-
mods
Library of Congress Outline Q: but which version, 3.3?
-
titleInfo
-
@usage
-
@supplied must be
yes
or no
-
@type
abbreviated
alternative
descriptive
transcribed
translated
-
title required in every collection
- often scripted, combination of other metadata fields (see example script from Syllabus Collection)
- only consistently used field under titleInfo
-
subTitle
-
name
- @authority see MODS values
datatel
millennium
lc
ulan
local
- @usage
-
@type
personal
corporate
conference
- namePart takes two different forms
Surname, Givenname
for students
Givenname Surname
for faculty
- namePartDate adhere to MODS
- role used in Archives to denote a photographer, etc. linked to AAT
- roleTerm
- @type "text" is only value
- subNameWrapper all CCA-specific fields, needed for EQUELLA repeaters
-
ccaAffiliated
must be
Yes
or No
, sentence case
- is student ID number in the CORE Waiver Portfolio Review collection
-
affiliation related organization, technically should be a level higher at mods/name/namePart
- should be CCA ID number in student work collections?
- in Libraries collection, it's the acronym of the college at the time
- in Communications' Images, it's non-CCA organizations affiliated with the photographer
- in Fashion Design, it's "Fashion partner" under the "Special projects" submission type
-
constituent values are
Alumnus
Faculty
Graduate student
Staff
Administrator
Undergraduate student
- NOT "Student" which is actually used in some places, should be converted
-
major
always from the Majors taxonomy
-
department comes from CCA Departments & Programs taxonomy
-
gradDate
always from the Semesters taxonomy
- description
free text, technically should be a level higher at mods/namePart
-
username = CCA username
-
staging previously used in CORE Waiver Portfolio, used in License Agreement to store phone
-
email
-
phone
-
typeOfResourceWrapper
-
genreWrapper
-
genre department-defined list in most student work collections, free text in Libraries (but we use 3 different authorities)
-
@type only value used is
style
in Libraries collection
-
@authority for Libraries, values are
-
originInfo
- place MODS has children which we don't use. We use for city of publication in Libraries.
- publisher
- edition
-
origininfo
-
dateType made up for Libraries collection, values in MODS case:
-
dateCreatedWrapper
-
dateCreated in ISO-8601,
YYYY-MM-DD
format
-
@qualifier either
approximate
or questionable
- @keyDate =
yes
, only one keyDate per record
- @encoding =
w3cdtf
(see standard)
-
pointStart this & below are for date ranges, not used in dateCaptured
-
pointEnd
-
staging used for when dates need to be processed via script before being stored, e.g. storing a true
YYYY
year value
-
dateCaptured
YYYY-MM-DD
again
- >
@encoding not used
- >
@qualifier
either
approximate
or questionable
-
dateOtherWrapper
-
semesterCreated linked to Semesters taxonomy, great overlap with local/courseInfo/semester
-
language =
eng
(set in Expert Scripting)
-
physicalDescription MODS only has single
<form>
child
-
formBroad uses AAT vocab, used across the board
-
formSpecific uses AAT vocab, only in Libraries
-
internetMediaType MIME types, only used in Libraries, can calculate by script
-
extent see Extent Terminology document, parallels MARC 300 in RDA
-
extentType unused
-
digitalOrigin MODS values are
born digital
reformatted digital
digitized microfilm
digitized other analog
-
physicalDescriptionNote used in Libraries, was an early attempt to work with repeaters (should be a noteWrapper under physDesc above)
-
note free-text
-
@type see MODS values (second table)
-
abstract mapped as the description for search results
-
tableOfContents used only in Libraries collection
-
noteWrapper
-
note
-
@type see MODS values (first table)
-
subject
-
subjectType our addition
-
topic
-
topicCONA a Getty authority, used in Libraries only
-
geographic
-
temporal used in Libraries only, starts with time periods related to college location/name, transitions into decades later
-
@authority not recorded, implicitly
local
-
name we don't use MODS sub-elements, populated via "LIBRARIES - Subject Name" taxonomy
-
@authority
-
@type
personal
conference
corporate
-
classification not used TODO: confirm
-
artstorClassification list box in Libraries collection
- @authority =
artstor
, set in expert scripting
-
photoClassification list box in CCA\C Archives subset of Libraries
-
relatedItem under MODS, any MODS element can be a sub-element of relatedItem. Used in Librares for major collection series (Hamaguchi, CCA/C Archives).
-
relateditem can link to any item
-
@type
preceding
succeeding
original
constituent
series
otherVersion
otherFormat
isReferencedBy
- title same as relatedItem above
- location
- note
-
originInfo
-
dateType
-
dateCreatedWrapper
-
dateCreated
- pointStart
- pointEnd
-
dateOtherWrapper
-
dateOther
- @type
- @encoding
- @qualifier
- pointStart
- pointEnd
-
identifier not used (TODO: confirm)
-
location
-
physicalLocation used only in Libraries, values are
Oakland Campus
, San Francisco Campus
, etc.
-
url
-
copyInformation MODS parent <holdingSimple> node removed
-
accessCondition =
For rights relating to this resource, please contact {{insert CCA department}}.
-
@type =
use and reproduction
-
part file UUIDs
-
@type
- detail number & title should be children of detail
- number should be default target for attachments
- numberB extra "number" elements are for circumstances (e.g. repeaters with multiple attachments) where the single element is too limiting
- numberC
- numberD
- title
- extent we don't use MODS child elements, see Extent Terminology & MARC 347 for guidance
- date
- text
-
wrapperOther TODO: is this used? These look like local fields.
- tags
- flaggedFor
- assignNumber
- exerciseNumber
- format
- formatSpecific
-
extension not used, for ad hoc MODS extensions (we use local)
-
recordInfo
-
recordContentSource =
cc9
-
recordCreationDate we don't use, but data is present in system-generated item data
-
recordChangeDate don't use, but present in system-generated item data
-
recordIdentifier filled in with item's UUID in Expert Scripting (see example)
-
recordOrigin not used
-
languageOfCataloging
-
descriptionStandard not used but should,
rda
is closest
-
local
-
archivesWrapper
- series parent series
III. College Life
- subseries subseries
3. Events
- seriesStaging full taxonomy term
III. College Life\3. Events
-
department
friendly department name, e.g.
Animation
-
division CCA divisions are:
Architecture Division
Design Division
Fine Arts Division
First Year Program
Humanities & Sciences Division
Interdisciplinary Studies
- academicLevel
-
courseInfo
-
department
five-letter all-caps department code, e.g.
PHOTO
-
semester
season + year, e.g.
Fall 2014
-
course
course title, e.g.
Material Assemblage
-
faculty
comma-separated list of faculty, e.g.
Jane Janane, Bob Bobob
-
facultyID
comma-separated list of faculty usernames, e.g.
jjanane, bbobob
note: not all programs record this, comes from course list taxos
-
section
specific section number e.g.
MARCH-555-01
-
firstYearDimension only used in First Year Program collections, values are two-character abbreviations:
-
courseinfo
full path from a course list taxonomy e.g.
Spring 2015\MARCH\Material Assemblage\Jane Janane\MARCH-555-01
these are the pieces that, split out, populate its siblings
-
courseCategory
various special groups of course like
Media History
, ENGAGE
, FYP dimensions, various interdisciplinary categories
-
specialPrograms
ecoTAP
seems to be the only value ever used, in Syllabus Collection
-
courseName
dept & course codes e.g.
MARCH-555
-
courseLevel
e.g. 100, 200, but I don't know where this is used and it should be entirely derivative of the courseName above
-
XList
Currently, section code of cross-listed course. Previously, an ID number of cross-listed course.
-
secondXList
ID number of another cross-listed course. Not used (hopefully)
-
courseWorkWrapper
- courseWorkType
values are
Assignment
Course work
Graduate First Year Review
Junior Review
Program Portfolio document
Senior thesis project
Senior packet
Special projects
Thesis
(note: only for grad programs, see "Senior packet" above for undergrads)
Workshop / Events
- courseWorkTypeSpecific
- imageType
- workType
-
groupProject
values are
group project
individual project
- groupProjectNumber
- groupConstituents
- groupMembers
- groupContribution
- material
- materials_freetext
- process
- assignmentTitle
- assignmentDescription
- assignmentDue
- assignmentDue_freetext
- assignmentLength
- assignmentLength_freetext
- assignmentReferences
- file
- fileA
- fileB
- projectTitle
- exerciseTitle
- submissionType
-
accreditation
often used to store a human-readable phrase composed of the local/assessmentWrapper fields e.g. "Fall 2014 External Review Photography"
- rating
-
juniorReviewWrapper
-
assessmentWrapper
data pulled from Assessment & Accreditation taxonomy
-
useInReview values are
-
type
e.g.
External Review
-
program
friendly name, e.g.
Photography
-
date
generally a semester, e.g.
Fall 2014
-
staging
for storing the full taxonomy term, e.g.
Fall 2014\External Review\Photography
-
seniorPacketWrapper
- title
- file
- hiResFile
- lowResFile
- fileTypeA
- fileTypeB
- fileTypeC
- semester
- date
- formatBroad
- formatSpecific
- formatOther
- heightINCH
- widthINCH
- depthINCH
- duration
- technique
- techniqueOther
- notes
- tags
- phase
- artistName
- viewLevel
-
viewLevel see how values map to user roles, values are
for internal X program use only
(where X = CCA program), typically the default
for internal X division use only
(where X = CCA division)
shared with other academic programs for assessment & accreditation purposes only
shared with college depts. and academic programs
shared with college depts., academic programs, and students
public
- exhibitWrapper for Senior Shows, Events, etc.
- type
- gallery uses CCA Galleries taxonomy but with optional "other" choice
- date often a date range that show ran
- title
- note often used as a gallery=other storage space
- showcardFile attachment
- installationShotFile attachment
- sponsor
- semester uses Semesters taxonomy
- tags
Legend
General Rules
- we always use "text" as the data Type in the Metadata Schema
- if something has "wrapper" in the name, it's there to work with EQUELLA's repeaters and should never house a value (be the target of a non-repeater Wizard control)
- "staging" fields are for housing taxonomy data which is later split out into other elements, never indexed for Power Search or searchable by free text
- camelCase elements generally adhere to MODS, all-lowercase do not