...
User Story | Notes | |
|---|---|---|
| 1 | User can enter a unique external system ID to import individual record data from an outside system into CollectionSpace | i.e. Not another CSpace instance Individual record - Object, Person, Acquisition, etc. |
| 2 | User can choose which system to import individual record data from |
|
| 3 | User can receive a visual and textual notice that the record is linked to data in another system | |
| 4 | User can refresh/update CollectionSpace records populated with data from another system | |
| 5 | User can refresh imported data per record or via batch process | |
| 6 | CollectionSpace system administrator can configure which outside systems are available to end users | |
| 7 | CollectionSpace system administrator can configure which fields to import from an outside system | |
| 8 | CollectionSpace system administrator can configure the data crosswalk between CollectionSpace and the outside system |
User interaction and design
...
- WIREFRAME IS DRAFT ONLY!
...
Open Questions
Question | Answer |
|---|---|
Should users be able to edit copied data? Edit fields in the record that weren’t copied over (i.e. if five fields in Cataloging contain data brought over from Voyager, can users add data to all the other fields)? | |
Do we want users to be able to “unlink” - i.e. now that the thing is copied over, they want it to have a life of its own in CSpace and over-write, edit, not refresh, etc.? |
...