Set Up Feed Importer for Libguides Databases

[kevinreiss]

Use the CSV output from https://github.com/pulibrary/lib_jobs/issues/442

This feed importer will populate the current Database content type with data now managed in libguides.

The fields that will be present in the CSV are listed in the issue linked above.

First Execute this in Staging, than repeat in Production

• [x] Remove alternative database title content type from search index.
• [x] Set Up Feeds Importer for Databases - Provide CSV URL in lib-jobs
• [x] Map CSV columns into Database content type fields.
• [x] Re-index databases; confirm search results are reasonable
• [x] Configure importer to run at the beginning of and conclusion of every workday.

[kevinreiss]

Overlaying the existing data isn't straightforward. The Drupal Node ID is the only possible overlay key for existing databases in the Drupal site. This is stored in the friendly_url in guides. We aren't assigning friendly_urls to new databases in guides. If we use this as match point we will need to make sure guide DB managers follow this practice.

[kevinreiss]

https://github.com/pulibrary/lib_jobs/issues/486

[kevinreiss]

the guide assets are now sync'ed up with the website. When the lib_jobs ticket 486 is done we can put a daily sync'd of the systems into production.

[kevinreiss]

Deployed prod. Will pull new database updates every hour. Closing