Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

16 results found

  1. Collection and circulation analytics would improve if we could import Create Lists item/bib search results into Decision Center.

    If so, Decision Center could aggregate Create Lists results (searches based on authorities, orders, or hold/patron circulation behaviours) to provide circulation and collection statistics.

    Our libraries would be satisfied for this import to display the fields that are in the “high”/ “low” circulation weeding reports.

    We understand that the aggregated statistics in Decision Center are generated the night before.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We would like to have a collection summary report based on item records with a count by item type and location. If possible, adding a limiter for circulation status, for example on shelf or checked out.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We use the hourly patron borrowing reports in Web Management Reports to track patron visits at offsite hold lockers. We would like to have this report migrated to Decision Center since this is the tool already in use by our frontline staff.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported. Best title normalized is particularly helpful for data brought into a spreadsheet as the removal of special characters and diacritics can greatly improving sorts and searching.

    These fields are available via SQL, where I make frequent use of them, but for most of our users Create Lists is the only option for extracting data from the system.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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,
    Elizabeth

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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 the hold_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...

    1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…

    31 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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…

    48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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…

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?