| Info |
|---|
Draft with notes and |
...
next steps |
Note: Process and documentation for initializing an authority required. Currently, Glen creates a record in the CSpace UI which initializes the default authority and creates a CSID. That CSID can then be used in the steps below.
1. Create at least one sample record each of your various record types.
...
(Notes:
- The Nuxeo web-based administrative interface comes with CSpace installation, and runs on port 8080
...
- .
...
- We need to check to see if complex catalog record is correctly returned, e.g., nested repeating elements, and having multiple schemas, having ampersands and other character entities.
...
...
- Need to confirm how we change nuxeo administrator password, both in nuxeo and in services configuration.
...
3. Use the Ruby script near the end of that document to take the records you export in step 2, and convert them to a format that the import service can ingest. You can do this manually, as well, but a script makes this easier. (Glen created an 'ed' script for the same purpose; you can ask him for that, if you wish.)
Note: We should rewrite this in groovy or something more standard. In the meantime, the ruby script should be in subversion. Multiple copies are sitting around. Aron will create a location for this, in a scripts directory.
...
5. Manually do whatever cleanup may be needed of characters or character sequences in the data itself that may trip up the import
service, either via search and replace, or using a 'sed' script, BBEdit text factory, etc. From what I recall, I had to do the following:
- unescaped
- un-escaped special XML characters need to be turned into XML entities - &, <, >, ', " Should be done in groovy or ruby script.
- XML entities need to be doubled (e.g., in the ruby or groovy script) (Should be fixed in ruby script, replacing with &)
- As well, you might look for dollar signs, which are triggers for macro interpolation. I didn't happen to run across any of those in the UCJEPS Person records, and so don't know first-hand how you might munge those. Maybe that is only an issue if the format is ${sometext}, so this might not be an issue.
6. Perform the import (curl, or wrap into the ruby-groovy script).
...