Skip to content

Matching the Workflow #4

@crhallberg

Description

@crhallberg

I think the next major step is to organize and perhaps consolidate all of the scripts we have to make it clear what order they need to be run in. Here are the steps I have written down as were recently acted on. Let me know if there are any differences between this and how you imagined your scripts to be used.

  1. Setup the database
    1. Run normalize_solr.py to get catalog list
    2. Gather course material (console.js)
    3. Run setup.py
    4. Edit the configuration file
    5. Run update.py
  2. Run reports.py
  3. Add class enrollment data to r2 (I have a new script for this)
  4. Send report off to Access Services, where they find potential ebook purchases
  5. Match potential ebook purchases against the database to find any we may already own
    1. Import into the database as a new list
    2. Run SQL query to find matches (I saved this query)
    3. Remove matches from the AS list
  6. Librarians use this list to determine which books to purchase
  7. Generate autocomplete file for AMP website (we haven't discussed this yet)

All of these steps are working but can be streamlined for easier and clearer use.

Also, it seems that there are places to reduce complexity. The new method that Access Services is using to match books (step 4) means we don't need to import publisher data anymore. Some of the reports weren't used but I believe it's important to keep them (at least in SQL form).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions