In our case, I am the one who's done most work in our Analytics so far, and I have created quite a network of folders and subfolders. I am often going into these folders and tidying things up. But it can still be quite overwhelming trying to navigate around in there.
Unfortunately there are some reports that I'd love to move to a subfolder, or at least rename to include the words DO NOT DELETE, but which I can't change because they're part of integrations set up for us by Ex Libris, and I don't want to break anything with those, so I've left those ones alone in our main Reports directory and just hope nobody else will touch them either.
Patricia Farnan | Application Administrator, Discovery Services
University Library | St Teresa’s Library
The University of Notre Dame Australia
Telephone: +61 8 9433 0707 | Email: [log in to unmask]
I respect and acknowledge the Nyungar Elders and the Wadjuk Nyungar people as the Traditional Owners and Custodians of this country on which I work.
From: Code for Libraries <[log in to unmask]> On Behalf Of Jonathan Sutherland
Sent: Thursday, 4 November 2021 2:51 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Analytics naming conventions
We just use a code prefix for every 'public' report (i.e. ones we intend to expose to staff via analytics objects). The code represents the Alma Analytics subject area (e.g. 'FUE-01 - Acquisitions Budget Summary' would use the 'Funds Expenditure' subject area.
For the analytics object title, we drop the code prefix and use a more easily understandable prefix to group them within the Alma UI Analytics menu (e.g. 'BUDGET: Acquisitions Budget Summary').
Collection Development Analyst & Developer
University of Waterloo Library
[log in to unmask]<mailto:[log in to unmask]>
From: Code for Libraries <[log in to unmask]> on behalf of Hammer, Erich F <[log in to unmask]>
Sent: Wednesday, November 3, 2021 1:02 PM
To: [log in to unmask] <[log in to unmask]>
Subject: [CODE4LIB] Analytics naming conventions
We have (belatedly) realized that we would be much better off with a firm naming convention for our Alma analytics reports. Currently, it's rather chaotic and nobody can identify what is important and what is left-over junk except (sometimes) the individual creators.
There are a few discussions about analytics naming conventions online, but they are focused on ecommerce sites. We can use some of their thinking to create our own convention, but I thought maybe my job could be a bit easier if someone else has already done this. ☺
So... Does anyone here have a working, analytics-reports, naming convention (and are willing to share it)?
Erich Hammer Head of Library Systems
[log in to unmask] University Libraries
518-442-3891 University @ Albany
"Extraordinary claims require extraordinary evidence."
-- Carl Sagan
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.