Metalib – Infogate

MetaLib Maintenance Workflow Documentation, 12/5/05
This is out of date – Documentation has been moved to the wiki

There are 4 MySQL tables that produce the InfoGate resources list and Library Resource Guide deep links:

• metalib
  All metalib resources except for Library Resource Guides are entered in this table. When new IRDs are added, activated, or deactivated this table must be updated.
  FIELDS: BRN_id, resource, config, resultstype, availability [free/subscription], status, sfxbutton, notes, date_added [added/updated]

• metalib2programs
  This table reflects selectors’ deep link choices. If an existing BRN Resource ID is replaced or deactivated, any links to that BRN Resource ID must be updated or deleted in this table.
  FIELDS: BRN_id, programid
  The two tables below were populated from a screen-scraping script written by Adam, our student assistant. We can run these scripts periodically if manual updating proves onerous.

• metalib_categories
  This table reflects all of the top-level subject categories in InfoGate. If subjects are added, changed, or deleted this table must be updated.
  FIELDS: meta_cat_id, meta_category

• metalib_dbs2cats
  This table reflects the assignment of resources to subjects. As these change this table must be updated.
  FIELDS: meta_cat_id, BRN_id

IRD CHANGES OR ADDITIONS:
When an IRD is added or changed, the MySQL database which is used to create lists of resources and Library Resource Guide deep links must also be changed. Run these queries and edit the BRN_id:
SELECT * FROM metalib
WHERE BRN_id = “BRN03222″
SELECT * FROM metalib2programs
WHERE BRN_id = “BRN03222″
SUBJECTS:
When a resource is assigned to a subject, the MySQL database needs to be updated. Add the BRN# and the meta_cat_id (found in the metalib_categories table) to the metalib_dbs2cats table.
When a resource is switched from a local IRD to a CKB IRD (or deactivated altogether, etc.) all subjects linked to that resource need to be changed. As there is currently no way to query the MetaLib application itself for a list of subjects that link to a resource, those subject assignments were added to the eresources MySQL database. To find subjects linked to resources run this query (using BRN03222 as an example):
SELECT * FROM metalib_dbs2cats
LEFT JOIN metalib_categories USING (meta_cat_id)
WHERE BRN_id = “BRN03222″
This should give a result that looks roughly like this:
117 BRN03222 117 English
128 BRN03222 128 History (American)
129 BRN03222 129 History (British)
135 BRN03222 135 History (Western Europe)
146 BRN03222 146 Literary Arts
168 BRN03222 168 Reference (John Hay Library)
Use the Categories Admin to assign the new Resource ID (say, BRN03706) to these subjects. Make sure to run the “All Subcategories” function.
Finally, update the resource ID in the MySQL database:
To edit one record at a time:
SELECT * FROM metalib_dbs2cats
WHERE BRN_id = “BRN03222″
To update with one query:
UPDATE metalib_dbs2cats
SET BRN_id = “BRN03706″
WHERE BRN_id = “BRN03222″

Preliminary thoughts about a maintenance workflow:
I’ve put all of the MetaLib resources in a MySQL table (except for the Library Resource Guides). In addition to serving as the basis for deep-linking selection for the LRGs this table also delivers lists of InfoGate resources to the web. See: http://dl.lib.brown.edu/eresources/infogate.php The list of “new” resources has everything that has been added or configured recently.
WORKFLOW: New stuff comes in either via a CKB update or by activating or adding an IRD.
CKB Update:
1) Web Services runs CKB update on a regular basis (weekly?) (set up cron job?)
2) Web Services posts the summary of new and changed resources to blog (see 8/12 entry).
3) Web Services activates new resources (consulting as needed), and tests resources where configurations have changed.
New Purchase / Vendor or Platform Change:
1) Anne activates, adds, or changes IRD in MetaLib
2) Anne posts new resources on the blog
3) Web Services tries to configure.
Steps 4-6 are the same for either CKB Update or New Purchase:
4) Web Services adds new or newly configured resources to MySQL table from whence they will appear on the web lists at the URL above.
5) Selectors use list of “new” InfoGate resources to notify Rosmary by a predetermined date if they want resources added to their LRGs
6) Rosemary updates category assignments in InfoGate and removes the “new” attribute in MySQL table