4 results found

1. Sierra 6.0 - Harvest Sierra data in MARC XML using OAI-PMH

   Idea Description: Libraries often share their metadata between our system and external systems. One very convenient way of keeping the databases in sync is using the OAI-PMH protocol. Sierra currently supports OAI-PMH as a harvester, but not the converse; as a repository. We would like to see this protocol implemented to allow external systems to harvest from Sierra to lower the amount of intervention required to keep the data in sync between Sierra and an external repository.

   Idea Value: Currently we use scheduler to generate review files and export data out of Sierra and transfer these files via FTP to external systems. This ties up several review files and is susceptible to review file failures as on occasion we have had the scheduled jobs fail or produce unexpected results and have to re-run them. Having this data harvested via OAI-PMH would free up these review files and remove the need to rely on Scheduler jobs. It would also reduce the amount of manual staff intervention required when sharing data from our Sierra system with new external parties.

   Idea Description: Libraries often share their metadata between our system and external systems. One very convenient way of keeping the databases in sync is using the OAI-PMH protocol. Sierra currently supports OAI-PMH as a harvester, but not the converse; as a repository. We would like to see this protocol implemented to allow external systems to harvest from Sierra to lower the amount of intervention required to keep the data in sync between Sierra and an external repository.

   Idea Value: Currently we use scheduler to generate review files and export data out of Sierra and transfer these files via FTP to… more

   0 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  ·  Cataloging & Metadata Management  ·  Edit…  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This enhancement was included in Sierra 6.0.

2. Sierra 6.2 - Verify Heading option for item record

   Could we please have the 'Verify Heading' functionality developed to apply to call numbers in item records?

   We used the 'Verify Heading' option for call numbers on item records for a long time since Millennium, that bug is fixed in Sierra 6.0. Now that feature only on bibliographic and authority records.

   (Refer to Solution ID:230706091757100 )

   6 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  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This idea has been included in Sierra 6.2.

3. Sierra 6.2 - Bulk Item level holds on same bib record

   Often times when items are moving from one call number to another, holds are placed on the items that are checked out in order to capture these items when they are returned so that any cataloging work can be done.

   The idea is to have an option to have some way that multiple item level holds can be placed on one bib record at the same time.

   Idea Value
   The value of this idea is staff time. By having to place individual holds on each item, this can take a long time when there are multiple copies of an item that needs to have a hold placed.

   Often times when items are moving from one call number to another, holds are placed on the items that are checked out in order to capture these items when they are returned so that any cataloging work can be done.

   The idea is to have an option to have some way that multiple item level holds can be placed on one bib record at the same time.

   Idea Value
   The value of this idea is staff time. By having to place individual holds on each item, this can take a long time when there are multiple copies of an item… more

   34 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

   6 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This idea has been included in Sierra 6.2.

4. Sierra 6.1 - Protect Global Updates on Server from accidental overwrite

   In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

   Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

   Idea Value
   This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

   As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..." dialog appears. If an existing update file is selected, it will be overwritten without a confirmation prompt.

   This behaviour makes sense after a set of saved parameters have been loaded but appears to be problematic at the start of a global update session.

   In particular, if the user makes this error immediately after accessing Global Update, the saved search is overwritten with a blank search (ask me how I know!); and in general, because Sierra does not prompt to confirm overwrite of a saved global update with an empty one having no parameters, it is easy to wipe out existing saves.

   The SDA UI could also potentially be tweaked to mitigate risk of this error by changing the order of entries in the "File" menu.

   Current state (grouped by Local/Sever, with "Save (Server)" and "Load (Server)" adjacent):Save (Local)Load (Local)Save (Sever)Load (Sever)Save as (Sever)

   Proposed state (grouped by Load/Save with separator between them):Load (Local)Load (Sever)-----------------Save (Local)Save (Sever)Save as (Sever)

   In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

   Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

   Idea Value
   This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

   As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..."… more

   17 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  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This feature has been included in Sierra 6.1.