6 results found

1. 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 a rare occurrence, but when it does happen it is critical that the data can be corrected to accurately reflect the dates for transaction.

   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… more

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.

   
   

2. 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 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 hold from the Sierra system.

   2. Hold ID: The hold_removed table should record the hold_id associated with the hold being removed. This would enable comprehensive tracking of a hold from its creation to its removal in the system.

   3. Link to Filled Hold Transaction: Ideally, the hold_removed table should have a way to link the removed hold to a filled hold transaction AND a hold placed transaction in the circ_trans table. This linkage would provide a complete history of the hold, including both the creation and removal events.

   Thank you for your consideration!

   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… more

   •  

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.

   
   

3. 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 checkin date".

   Thank you,
   Elizabeth Wright

   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… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.

   
   

4. 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 forward.

   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… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.

   
   

5. 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 location and item type; by transaction location and item type or by transaction location and material type). For consistency sake, these reports would have the same filter options for time.

   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… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.

   
   

6. 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,
   Elizabeth

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Reporting & Analytics (incl Decision Center)  ·  Delete…  ·  Admin →
   CLOSED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.

   
   

   This idea is still available for commenting but is no longer eligible for voting.

   
   

   Ideas that were submitted three or more years ago are archived for future reference.