Difference between revisions of "Development/Functional testing/Export/import tests"
From AtoM wiki
(Migrating content from qubit, updating and editing where relevant) |
m (Minor tweak to page title and breadcrumb) |
||
Line 1: | Line 1: | ||
− | [[Main Page]] > [[Development]] > [[Development/Functional testing]] > Export/import tests | + | {{#pagetitle: Export/import tests }} |
+ | [[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Export/import tests | ||
Latest revision as of 17:53, 12 August 2014
Main Page > Development > Development/Functional testing > Development/Functional testing/Export/import tests
Information objects
- EAD export option appears in all information object show screens
- DC export option appears in all information object show screens
- MODS export option appears in MODS show screen (ie. when template is switched to MODS)
- Clicking EAD export exports current information object plus all child records and related authority records, repository records, subject access points, place access points and name access points
- User can export and import large fonds - eg. parent with 80 or more children
- When importing EAD, DC and MODS files, the files include all data that were in the original information object (where it is possible to map them)
- All data map to the correct fields
Actor objects
- EAC export option appears in actor object show screen
- Clicking EAC export exports the actor object
- User can import EAC files by going to Import > XML and selecting an EAC file
- When importing EAC files, the files include all data that were in the original actor object
- All data map to the correct fields
Taxonomies
- SKOS export and import options appear on taxonomy list and show screens
- Clicking SKOS export exports current term and all narrow and non-preferred terms
- User can import SKOS files from taxonomy show screen or by going to Import > XML and selecting a skos file
- (NOTE: importing a SKOS taxonomy for places through the Import > XML option currently results in a subject taxonomy, not a places taxonomy. This is a known issue - see issue #4247 for the implemented solution/workaround)
- When importing SKOS files, the files include all data that were in the original taxonomy (except Related Terms)
- All data map to the correct fields
- Source notes become URLs to original terms