Git Product home page Git Product logo

library_data_warehouse's Introduction

License

Penn State Libraries Data Warehouse

This is the public facing content for development of the libraries data warehouse at Penn State. The content here is a result of the Datawarehouse Steerign committee's work and intended as an open source resource for anyone, especially libraries wishing to learn from our work or conversely contribute.

Much of the content will be in the wiki, so please check that out as well.

Personas developed for this committee are housed at https://github.com/psu-libraries/personas

Much of the work in the form of issues for data source and features are noted as issues. A more organized and prioritized view of the issues can be found at https://waffle.io/psu-libraries/library_data_warehouse.

The personas used for this project are

Committee Membership

Steve Borelli (co-chair)

Robert Olendorf (co-chair)

Julia Proctor

Nathan Piekielek

Sherry Lonsdale

Matt Ciszek

Using

If you use content from this project, please acknowledge or cite us. DOI will be generated soon.

Contributing

The documents in the repository are currently being created and written by the committee as a report to the administration. Suggestions are welcome, however, a full open review of the contents of this project will be done after admin review.

library_data_warehouse's People

Contributors

olendorf avatar sborrelli avatar

Watchers

avatar avatar avatar avatar avatar

library_data_warehouse's Issues

Reference/Consultations

  • Sources: Desk Tracker, Ask-a-Librarian, Search Bar 9i.e. Peer research Consultants)

  • Contacts: Tom Reinsfelder (Ask), Hailley Fargo (Search Bar)

  • schema

  • data dictionary

  • ingest

Data Learning Center Usage

-Does this seem appropriate as a separate issue or should it be integrated into reference/consultations?

  • Source:

  • Contact:

  • schema

  • data dictionary

  • ingest

Event/Exhibit Attendance

Events and Exhibits may be better as independent issues.

  • Source:

  • Contact:

  • schema

  • data dictionary

  • ingest

Database Access

-Should aim to include databases, journals, websites, Repository, maybe ILL (if not included elsewhere)

  • schema

  • data dictionary

  • ingest

Foo Data

  • schema

  • data dictionary

  • ingest

Endowment funds data

Allow endowment recipients, perhaps donors and others know what is in the account, what needs spending etc.

Instruction Statistics

-Should include the full scope of the instructional landscape. The landscape is being worked out by LLS and the ISC as of 04.19.18
- This may benefit from separating by type of instruction (see LDSS-DataDict from Univ. Minnesota)
-Types of instruction documented to date and desired components for each. This is an incomplete draft

  • Course-related instruction
    -- Course ID
    --Date
    -- Time spent preparing for session
    --lesson plan (upload option)
    --up to 3 learning outcomes addressed
    --Description of communication with instructor
    --learning activities employed
    --materials used (upload)
    --materials used description of
    --some variety of follow-up activities

  • Embedded librarianship

  • Orientation
    -- event name
    -- brief description of event
    -- outcomes
    -- number of participants
    -- participant identifier
    -- date of orientation event

  • outreach
    -- affective outcomes

  • student engagement
    -- outcomes

  • Digital badges

  • Tutorials
    -- credo modules (as a subset of tutorials; this will likely have somewhat unique sub-fields)

  • Train the trainer

  • Source: Digital Measures (tentative)

  • Contact: Rebecca Miller

  • schema

  • data dictionary

  • ingest

Patron Count -Desk Tracker

  • Sources: Desk Tracker, Ask-a-Librarian, Search Bar 9i.e. Peer research Consultants)

  • Contacts: Tom Reinsfelder (Ask), Hailley Fargo (Search Bar)

  • schema

  • data dictionary

  • ingest

E-Book Usage

-Maybe a subset of Circulation data

  • Source: Serials Solutions (Intota), Ebook Central, EBSCO ebooks, Elsevier, individual vendors

  • Contact: Jaime Jamison (Acquisitions), Carolyn Hertzog (Acquisitions), Julia Proctor (Collection Services)

  • schema

  • data dictionary

  • ingest

Collection Development Data

Be able to link to purchases and circulation

Be able to quickly see how much is left to spend to help planning

Makerspace

  • Source:

  • Contact:

  • schema

  • data dictionary

  • ingest

Patron feedback

This should be envisioned as providing a place for recording individual feedback. It should be designed such that feedback that is relevant to multiple units can be mapped as such. Fields should include:
Source (of feedback)

  • Date
  • Patron type
  • Unique identifier for patron (possibly)
  • Source of feedback ID or other identifiers (name of feedback mechanism)
  • feedback prompt (the specific question being responded to)
  • feedback/patron comments
  • unit(s) to push feedback to

Group Study Room Usage

  • Source: LibCal
  • Contact: Ann Thompson
  • schema
  • data dictionary
    Is this where this information goes?

Source

This is from the API: Endpoints 1.1 (https://psu.libcal.com/admin_api.php). It is room reservation data from LibCal.

Fields

  • /calendars Retrieve a list of all public calendars

  • /calendars/:id A calendar id or list of calendar ids to retrieve

  • /events This has six Query String Parameters. Do I need to list them all here?

  • /events/:id

  • var2: <integer: 16> access_level_private this is an id for data on another table.

  • ingest

3-D Printing

  • Source:

  • Contact:

  • schema

  • data dictionary

  • ingest

ILL

-This could be a subset of Circulation data

  • Source: Illiad

  • Contact: Meg Massey

  • schema

  • data dictionary

  • ingest

Strategic Planning

  • schema
    Variables and functions needed:
  • University Strategic Plan Thematic Priority Areas
    • University Strategic Plan Thematic Priority Area goals
      • University Strategic Plan Thematic Priority Area goal strategies
        • University Strategic Plan Supporting Elements
  • President Barron’s initiatives
  • University Libraries Programmatic areas
    • University Libraries Programmatic area goals
      • University Libraries Programmatic area goal objectives
        • University Libraries Action Plan
          • Action
  • University Libraries foundational values
  • University Libraries Action Plan
    • Action
    • Timeline
    • Deliverables
    • Sponsor
    • Status
  • University Libraries Action Plan Teams
    • Charge
    • Deliverables
    • Timeline
    • Membership
    • Chairs
    • Sponsors
    • Status
    • PSU Strategic Areas ( = University Strategic Plan Supporting Elements)

Needed function:

  • All actions of University Libraries Action Plan Teams need to be mapped to the University Libraries and University Strategic Planning structure.

  • Needs to be flexible and extensible to accommodate evolving strategic planning models

  • Should be able to push prompts for updates to appropriate sponsor or chair as needed

  • data dictionary

  • ingest

Reserve Usage

  • Source: Workflows

  • Contact: Chris Holobar

  • schema

  • data dictionary

  • ingest

Equipment Checkout

  • Sources: web checkout (MTSS), BlueCloud (I think)

  • Contacts:

  • schema

  • data dictionary

  • ingest

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.