Data requirement for reporting online requesting

[taceybadgerbrook]

What is it and who's it for?

Data for Tania Williams

User story

As a Library Assistant

I need to report on levels of online requesting

So that Collections understand which areas are being accessed and which are not

Implementation

Data to be accessable in Kibana conversion* index

Acceptance criteria

1. User category (eg Graduate/Undergraduate - part of registration data)
2. Staff/non-staff status
3. Location code (enables more detailed analysis that workType)
4. Call num (enables more detailed analysis of type of collection)
5. Title
6. Subject (yes, even though these are not standardised)
7. Delivery destination (eg RMR or Library enquiry desk

Testing and tracking

Tacey to set up Kibana dashboard for Tania and/or provide access to monthly csv

[taceybadgerbrook]

I appreciate that not all of this data has been planned as part of online requesting but first I need to understand what is and is not possible so that I can go back and have the conversation with Tania.

[taceybadgerbrook]

I have taken out location code and call num from the list above as these are not in the API and there are no plans to include them.

[taceybadgerbrook]

@davidpmccormick @GarethOrmerod @jamesgorrie could the following be made available in Kibana?

• user category (eg graduate/undergraduate - from registration data)
• staff/non-staff status - from registration data)
• delivery destination

[taceybadgerbrook]

Tania would like to use the location code and call num data to produce tables on specific collections and types of works (eg zines, medical books) as workType is not specific enough:

The staff/non-staff data would be used to provide a filter so that Collections staff can assess whether demand for certain types of material is staff or non-staff led. The delivery destination data is so that Library staff can decide whether or not to change their processes to make them more efficient.

[taceybadgerbrook]

@jamesgorrie I'm looking for the field in the sierra indices in Kibana that hold subject information as part of the requirement for the online requesting data. My hunch is that this is somewhere in sierra_varfields but don't know what the marcTag it is.

Also, if we could have a call about how the sierra indices are organised would be great.

[taceybadgerbrook]

@jtweed a summary of the data requirement and business case is in this document.

In a nutshell, Collections and Research need data for operational purposes as well as for developing the Collection. The plethora of data listed in this spreadsheet which includes examples in the example tab is due to the fact that Sierra fields have been used for different purposes over time, making it impossible to identify items using just one field.

[taceybadgerbrook]

Objectives for the platform and how the Collections and Research business cases support these:

Researchers find more of what they're looking for in our collections

• Develop popular Collection areas
• Improve catalogue metadata
• Prioritise areas for cataloguing
• Prioritise items for digitisation
• Assessment of impact of digitisation

Researchers engage with a broader range of our collections

• Increase diversity of Collection
• Planning public events

Build trust and reduce barriers for visiting and online audiences

• Reduce access restrictions

[taceybadgerbrook]

Business cases outside of platform objectives:

• Suggest additional material for researchers
• Staff planning
• LED/RMR storage planning
• Locate missing items
• Cost-effective retrieval and storage of items
• Saving money on subscriptions

[taceybadgerbrook]

Some dummy dashboards:

[taceybadgerbrook]

Dummy dashboards:

[pollecuttn]

Awaiting data from requesting

[taceybadgerbrook]

This ticket will be addressed after https://github.com/wellcomecollection/wellcomecollection.org/issues/7132