Digital.Grinnell
Call it The GCDLADB if you like.
Mounting //STORAGE for IMI Ingest in Digital.Grinnell 2 min read Jul 22, 2019 | Updated: Nov 12, 2020 08:30
Claiming another small victory today! Why? Well, the Digital.Grinnell instance of IMI (Islandora Multi-Importer) module is customized so that choosing “*local” as an object ingest source invokes a hook function I created in our DG7 module. That hook enables IMI to “find” named files/content (things like PDFs, images, etc.) in the Grinnell College //STORAGE server. //STORAGE can be mounted as a CIFS (Common Internet File System) and used to drive ingest if the right package/drivers are made available to Islandora. That can be a little tricky in ISLE, but it’s manageable. ...
Staging Digital.Grinnell (DG) on DigitalOcean (DO) 7 min read Feb 11, 2020 | Updated: Mar 2, 2020 16:13
ISLE v1.3.0 has been running on my staging server, DGDockerX, for months now and it seems to be performing as-expected with one exception… when I try to import a batch of objects using IMI, the Islandora Multi-Importer, I get the following error: The website encountered an unexpected error. Please try again later. Examinations of Recent log messages seem to point to DNS issues that I’m unable to overcome because I have no control over our DNS records, campus networking, or firewalls. ...
Digital.Grinnell's IMI Workflow 5 min read Aug 21, 2019 | Updated: Sep 16, 2019 22:11
Note: The abbreviation IMI is used frequently in this post to represent the Islandora Multi-Importer, a CSV-file-driven batch ingest tool used by numerous institutions in the Islandora community. Also, while updating this post I found this gem… Diagrams in Documentation (Markdown Guide). This post is an addition to the discussion in post 028, Mounting //Storage for IMI Ingest in Digital.Grinnell which was written largely to remind me how the //Storage mount works. 😕 Unlike post 028, this post is meant for myself AND for others at Grinnell College who prepare digital objects for ingest via IMI. ...
PDF Ingest in Digital.Grinnell 2 min read Jul 24, 2019
A set of 21 PDF objects were ingested into Digital.Grinnell’s Faculty Scholarship collection using IMI on 22-July-2019; unfortunately none of these PDFs contained OCR (optical character recognition) or “text recognition” data, so none of them generated a valid FULL_TEXT datastream. FULL_TEXT datastreams are required to make PDF, and similar text content, searchable and discoverable in Digital.Grinnell. In order to confirm that the lack of OCR was in fact the problem, I ran a little test on https://digital.grinnell.edu/islandora/object/grinnell:26702, one of the 21 objects. ...