14 results found
-
Include zero results for selected locations in all reports in Decision Center
Currently Decision Center only returns data for a location parameter if there was activity for the selected time period and does not return a zero placeholder for locations without activity. This creates extra work for staff when working with the resulting Excel files. They can't easily reference the cells in Excel consistently.
3 votes -
Decision Center: Identify titles eligible for stock rotation in pooling locations
We have a floating collection and use Decision Center to manage our collection. We need to know what is on the shelf OR not on the shelf at multiple sites. To do this, we use excel pivot tables to manipulate the "low circulation weeding reports". I have attached the workflow and the result.
After pivoting the "low circulation weeding reports" (searching for items that have circulated less than 300 times in 1 month at multiple branches) our result includes everything on the shelf at multiple branches. The pivot table allows us to identify which titles are at a branch AND…
2 votes -
Sierra 6.1 - Add item status date to Create Lists
It would be very useful to be able to at least export (if not also filter/search on) the status date in Create Lists. We do things like delete items that have been in certain statuses for a certain number of months, and used to have to guess based on the updated date, but obviously records can be updated without the status being changed. Going forward (as newer items get status dates associated with them) we can check item-by-item by mousing over the status in the item record, but it would be a big help to have the date appear alongside…
3 votesThis idea is already on the product roadmap and will be included in Sierra 6.1.
-
Decision Center: Pooling Report not based on demand
The Pooling Report generates a list of titles where "the pooling branch has more copies than it needs to meet 150% of demand". This is not the only reason that multi-branch libraries with floating collections have pooling collections.
Items in a floating collection can be returned to any location.
Could we have a pooling report that identifies:
1) Titles that have never been assigned or checked out at the location of the drought location
AND/OR
2) Titles not held at the drought location
Thank you,
Elizabeth2 votesThe product manager will review this idea for possible inclusion in a future release.
-
Decision Center Turnover Reports - Consistent Parameters
Decision Center has a number of Turnover reports available. However, not all of them allow you to choose Year and Month as one of the initial filters. For example, I normally look at the turnover by branch report each month. In early July (our fiscal year runs July 1 - June 30) I went to view the June report and was unable to see that, could see the annual totals for previous fiscal years. Only during the current fiscal year are you able to see the monthly breakdown. However, this is not the case with other turnover reports (by owning…
4 votesThe product manager will review this idea for possible inclusion in a future release.
-
Allow missing Web Management Reports Data to be re-added with the correct time period
Twice in the past year we have encountered errors in which the overnight statistics process did not complete leading to a missing day's worth of transactions in Web Management Reports. In both cases we only learned of this missing data later upon running monthly reports and finding an undercount.
Upon being alerted Innovative has been able to retrieve the missing data and add it back to WMR, but doing so adds it to the current month instead of the correct timeframe. This latest occurrence crossed fiscal years for us, essentially breaking the reporting tool for our needs.
Fortunately, this is…
9 votesThe product manager will review this idea for possible inclusion in a future release.
-
More reliable data around Holds: Don't delete Holds in the `holds_removed` Sierra DNA table!
Data in the
hold_removed
table is being deleted before the 60-day retention period is up in situations where staff clear the hold shelf, and an entry in thehold_removed
table is indicated to be "picked up". This is unexpected and not helpful in the task of gathering more data related to holds.I propose the following changes...
Retention Period: Entries are being removed from the hold_removed table before the default 60-day retention period is up. I propose that data should remain in this table, as it represents the lifecycle of a hold and the recorded event that removed an active…
9 votesThe product manager will review this idea for possible inclusion in a future release.
-
Add "item status date" to Decision Center reports
Libraries use Decision Center to determine what is not circulating or what has been at the Branch for a long time without circulating.
The new "item status date" added in Sierra 6.0 could help Decision Center identify items that were moved to a branch but have not been checked out (eg. items get to the new branch by using CIRCA's item status change from "checked in" > "in transit" > and then are checked in at the new branch)
Reports that would benefit from this would be the Maintenance Report or any report that lists a "created date" and "last…
7 votes -
Decision Center Before and After Floating Statistics
We're interested in evaluating how well our Floating Collections are performing to see if it's benefiting specific locations or ranking specific location codes preferably, but not necessarily limited to, change of circ or transit wait time post-float at branches to determine what should and shouldn't float for that branch going forward based on past performance. Besides the drought report in Decision Center, this information appears to be lacking. We'd like for reporting capabilities to be added to its data to help inform decision-making in terms of tweaking Floating Collections location codes to keep and which to return to non-Floating going…
6 votes -
Sierra user tracking
Provide data for tracking Sierra users (library staff). For example, log sign on and sign out dates and times. Perhaps add a "Last signed in" date field to the user record. Other data points might also be worthy of recording, such as types of records accessed.
Idea Value
Given that libraries handle possibly sensitive personal data, system users who have access to such data should be trackable. Currently, it's not even possible to find when the last time a user has signed on to the system.29 votesFUTURE POSSIBILITIES (IDEA LAB) · 3 comments · Reporting & Analytics (incl Decision Center) · Admin → -
Retain more than 36 months of Sierra data for reporting
Innovative explains that Sierra is hardcoded to retain the source circulation statistics for Web Management Reports only up to 36 months, but longer data series are needed, because the Library can make better decisions and optimize services only if we know facts, and facts are better known when seen on a larger time span. "Old data for new decisions".
This change could help both Library managers and staff to understand facts and their trends, and to see whether and how something should be changed. Three years are too few to see facts, but knowing that certain sections of the Library…30 votesFUTURE POSSIBILITIES (IDEA LAB) · 1 comment · Reporting & Analytics (incl Decision Center) · Admin → -
Add create date; last use date; and login Create Lists: Saved Search, Saved Sorts, Saved Lists, Saved Exports
In Create Lists the system saves the login and the date that the Review File was created. Please extend this feature to: Saved Search, Saved Sorts, Saved Lists, Saved Exports; to make annually cleaning these saved features easier.
Additionally add a last used date to create lists, and the above saved features to know if it is no longer in use.
Idea Value
At present I have to tell staff to add the date and their username in the title to system cleaning. This idea would save a great deal of time when it comes to purging unused saves in…47 votesFUTURE POSSIBILITIES (IDEA LAB) · 6 comments · Reporting & Analytics (incl Decision Center) · Admin → -
Allow Local Create List Saved Exports
Create List supports "Apply Saved Export." However, it has a 100 max limit. In large institutions or consortiums users hit this limit. This requires users to manually configure what can be complex export data by hand every time.
Sierra's Create List supports loading locally saved queries via JSON. Global update allows the user to Load (Local) commands. Extend Sierra's Create List to Load (Local) saved export fields. This increases efficiency and eliminates errors.
Idea Value
In our institution, there are no available Saved Export slots. As a result we often have to configure complex export data by hand. This introduces…20 votesFUTURE POSSIBILITIES (IDEA LAB) · 0 comments · Reporting & Analytics (incl Decision Center) · Admin → -
Add Year of Publication to export options in Create Lists
Currently we are only able to export "Pub Info" from the bib record, which contains both the publisher's name and the date(s) of publication. The format of the data in the field is variable and sometimes contains multiple years of publication, making it extremely difficult to pull out the correct year.
Adding the pubdate field from the bibrecordproperty table to the export options in Create Lists would give us that data very easily.
Idea Value
Having the pub year for an item lets us analyze the age of the collection, which is particularly important in nonfiction. Some subject…18 votesFUTURE POSSIBILITIES (IDEA LAB) · 2 comments · Reporting & Analytics (incl Decision Center) · Admin →
- Don't see your idea?