Difference between revisions of "Archivists Toolkit integration"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
[[File:Metadata_entry_2.png|380px|thumb|center|]] | [[File:Metadata_entry_2.png|380px|thumb|center|]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
====Text file field mapping==== | ====Text file field mapping==== | ||
Revision as of 16:50, 17 September 2012
Main Page > Development > Development documentation > Integration with Archivists' Toolkit
Workflow
DIP requirements
Metadata entry templates
Example 1
Text file field mapping
- From data entry:
- Use statement --> useStatement
- Restrictions apply? --> restrictionsApply
- Is component --> FALSE
- Object type --> objectType
- Date expression --> dateExpression
- Date begin --> dateBegin
- Date end --> dateEnd
- Auto-populated:
- digitalObjectID (file UUID)
- title (filename without extension)
- url (filepath and filename)
- existenceLocationOriginals (AIP UUID)
Example 2
Text file field mapping
- From data entry:
- Parent digital object ID --> digitalObjectID
- Use statement --> useStatement
- Restrictions apply? --> restrictionsApply (TRUE)
- Is component --> isComponent (TRUE)
- Object type --> objectType
- Date expression --> dateExpression
- Date begin --> dateBegin
- Date end --> dateEnd
- Auto-populated:
- digitalObjectID (file UUID)
- title (filename without extension)
- url (filepath and filename)
- existenceLocationOriginals (AIP UUID)