SFU data migration

Main Page > AABC Data Migration Toolkit > SFU data migration

= Overview =



= Extract =

= Transform =

Table: NME__Name
Alternate forms of name. We are only migrating "Previous form of name".

Table: RLT__RelatedTerm
The SFU data uses two reciprocal rows to describe (most) term relations with a different predicate for each. For the migration only the first relation is used (the row with the smallest "_kplat__relatedTermID") and a concatenate string is used to create a subject-predicate-object descriptive statement.

= Load =

= Notes =

SFU system documentation
SFU AIS documentation

2010-Dec-10 meeting
Present: David (Artefactual), Richard and Paul (SFU Archives).

Archival descriptions
https://wiki.sfu.ca/departments/archives/index.php/AIS_ICA-AtoM_Field_Mapping:_Archival_Description


 * Richard to add "parent_id" field to FMPro to facilitate migration
 * Series table self-relates?
 * Yes. Capped at three levels - series, sub-series and sub-sub-series. All three levels are included in SFU 6-place hierarchical numbering system (e.g. "F-202-1-0-0-2-118")
 * Gap: RetrievalDescription table?
 * Used for physical access control. Not migrating in pilot.
 * Gap: Holding table?
 * Used for records management. Not migrating in pilot.
 * Will calc Level of Description in FMPro during migration
 * File::accessStatus__lat, Item::accessStatus__lat - gap in workflow (controlled vocab, default status to "pending review")
 * Can implement SFU vocab via taxonomy and migrate directly (no mapping)
 * For pilot default status will be migrated from system. May still be a workflow gap in the future if all descriptions are entered via ICA-AtoM.
 * RADNoteOther - keep as a single "blob" (don't break field by headers).
 * AccessPoint::heading__lxt
 * Add RAD GMD terms to "subject" taxonomy to replicate existing usage as subject access points
 * Ignore qualifier for amount of materials for pilot.
 * Officers are a special name access point relation
 * Description A -> corporation Acme -> officer Andy
 * Officers must be listed in description A to be included in access points according to RAD
 * Migrate officer (Andy) as name access point for Description A
 * Migrate corporation Acme as authority record linked to Description A
 * In migration, concatenate list of officers of corporation Acme to the "Admin history" field for corporation Acme
 * Institution identifier & Rules or conventions - not necessary to create a field in FMPro, will set during tranform
 * *::recordStatus__lat
 * duplicate SFU vocab in ICA-AtoM taxonomy
 * Don't migrate "superseded" or "obsolete" descriptions for pilot.
 * ::recordStatus__lat - workflow gap "set to 'Provisional' on creation. Not a concern for pilot.
 * Language & script of description - set in migration tool
 * Fonds::faPreparedBy__lxt - store in "Date of creation, revision & deletion"?
 * Fonds::faFinancialAssistance__lxt - migrate to General note field for now, no better mapping in RAD.
 * Don't migrate version history

Authority records
https://wiki.sfu.ca/departments/archives/index.php/AIS_ICA-AtoM_Field_Mapping:_Authority_Record
 * Type of entity - set during transform
 * Authorized form of name - Richard will create a separate field for Persons in FMPro to get name in "Last, First" format. Migrate this name instead of "authorized form"
 * Other name - just migrate previous titles (have previousTitleFlag__lct flagged)
 * Most of fields not used, and have inconsistent data, so we will not migrate
 * Migrate all identity area
 * Migrate dates and history from description area
 * Don't migrate rest of authority record data
 * Relations
 * SFU will map SFU entity relation terms to ISAAR terms (hierarchical, family, temporal, associative)
 * Use SFU relation term to generate descriptive text for relation "e.g. Corp A supervises Corp B".
 * SFU relations are contextual (e.g. parent Person A/ parent of Person B), will make generic for ICA-Atom (e.g. Person A parent of Person B).

Online finding aids

 * e.g. Online finding aids: http://www.sfu.ca/archives2/F-3/F-3.html