As we start to build out these databases, I'm accumulating a list of tasks that can only be done at the command line, but which we currently have to ask HBR (Systems) to do:
- Rebuild the search index:
php symfony search:populate
We have to do this every time we make changes directly in the db; and there are lots of such changes to be done, because the UI for the app is based around editing individual records, so there's no way to (for instance) change the status of a bunch of records we've imported from CSV to "published" without editing the db. - Import digital images:
This happens when we've bulk-uploaded archival description records for a specific repository using the CSV route, but we then want to upload a digital surrogate (picture of the object) for each record. It requires uploading the digital images themselves to a directory on the server, along with a CSV file that links each image to an identifier in the db, and then running:
php symfony digitalobject:load /path/to/your/loadfile.csv
- Exporting data in EAD (XML) format:
Some of our repositories are using this aggregation process to create AtoM records which they will then import back into an AtoM instance of their own (Nanaimo is going to be doing this). The process for this involves bulk-exporting all the archival descriptions associated with that repository in EAD format:
php symfony export:bulk --criteria="i.repository_id = (SELECT object_id FROM slug WHERE slug='example-repo-slug')" /path/to/my/exportFolder