Item Importances
Background
Items on lists can be given a level of importance. This is used to indicate to students that they may wish to pay more or less attention to certain works.
Libraries often use the item importance in their purchase decision making processes and so want to track items which have importances and those that don’t
Questions you might be asking
- How many items don’t have importances?
- Which departments are not using importances?
- Do Essential Reading items get more views than Further Reading items?
- When we are reviewing lists is it worth paying attention to items marked as Background Reading?
- Are academics flagging everything as Essential?
Events
This recipe includes some queries that use events.
There are a few things to be aware of when working with events in Talis Aspire Advanced MIS. Events are grouped into time windows with a count or sum per time window. Events are available for the last 30 days with a 1 hour granularity, and for the last 36 months with a 1 day granularity. Also as Talis add more events into Advanced MIS you may want to check when the first event of a particular class appears, as it may not be available for the full time range you are interested in.
Here are a couple of queries to see how far back event data is available:
-- data available since:
select min(time_window) from f_event_timeseries_24hr;
-- data available since for specific event:
select min(time_window) from f_event_timeseries_24hr
WHERE event_class = 'list.item.external_link.click';
It may be that there are different dates returned. For example, the reading intentions were only added to Advanced MIS from December 2018, but we have events in the database going back to May 2018.
A Basic Query
We start with a simple query to find out how many items do not have an importance set.
-- count the items
select count(item_guid)
from f_rl_items
where importance = '';
-- which items are they?
select item_url
from f_rl_items
where importance = '';
We could then look to see how many items there are for each importance type:
select importance, count(importance)
from f_rl_items
group by importance;
Which gives something like
importance | count |
---|---|
7863 | |
Recommended | 4211 |
Suggested for student purchase | 700 |
Essential | 2289 |
Optional | 1981 |
Linking importances to the hierarchy
We need to know that lists are linked to the hierarchy, and items are linked to lists. We need to also know about the hierarchy, for example that there are schools or departments which have modules, and it is these modules which are linked to lists
select
hierarchy.url,
items.importance,
count(items.importance)
from
f_rl_items items,
f_rl_hierarchy_descendants hierarchy,
f_rl_lists lists
where
-- join lists to the hierarchy
lists.hierarchy_url = hierarchy.url
and
-- join lists to their items
lists.list_guid = items.list_guid
and
-- look for only nodes in the hierarchy that have a descendant of type 'Module'
hierarchy.descendant_url
in (
select url
from f_rl_hierarchy
where type = 'Module'
)
group by
hierarchy.url,
items.importance
order by
hierarchy.url,
items.importance
;
This might give us something like this which can then be processed into a chart
url | importance | count |
---|---|---|
http://demo.talisaspire.com/courses/buseco | 1 | |
http://demo.talisaspire.com/courses/buseco | Essential | 3 |
http://demo.talisaspire.com/courses/buseco | Optional | 2 |
http://demo.talisaspire.com/courses/buseco | Recommended | 5 |
http://demo.talisaspire.com/courses/buseco | Suggested for student purchase | 1 |
http://demo.talisaspire.com/courses/gol001 | 2 | |
http://demo.talisaspire.com/courses/hum110 | 4 | |
http://demo.talisaspire.com/courses/hum110 | Essential | 1 |
http://demo.talisaspire.com/courses/hum110 | Optional | 1 |
http://demo.talisaspire.com/departments/acc001 | 12 | |
http://demo.talisaspire.com/departments/man01 | 198 | |
http://demo.talisaspire.com/departments/man01 | Essential | 264 |
http://demo.talisaspire.com/departments/man01 | Journals | 231 |
http://demo.talisaspire.com/departments/man01 | Optional | 33 |
http://demo.talisaspire.com/departments/man01 | Recommended | 495 |
http://demo.talisaspire.com/departments/man01 | Suggested for student purchase | 132 |
http://demo.talisaspire.com/modules/inv101 | 27 | |
http://demo.talisaspire.com/modules/inv101 | Suggested for student purchase | 4 |
http://demo.talisaspire.com/schools/bs02 | 735 | |
http://demo.talisaspire.com/schools/bs02 | Suggested for student purchase | 49 |
Assumptions and limitations
- It may be that importances are not consistently added to items.
- It may be that items in previous time periods did not have importances set as rigorously, or that the definitions of what the importance means have changed over time, or between departments.
Things to try
You could also now link in the f_event_timeseries_24hr
table, looking for list.item.view
events linked to the items that have importances.