24 results found
-
MFT support in data exchange
Prior to Sierra 6.0 and the introduction of MFT, it was possible to use FTP to transfer files though data exchange within Sierra. This is no longer possible as MFT is not supported in data exchange.
Please add support for MFT in data exchange in the same way as support for MFT has been added in scheduler.11 votesIn 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.
-
Allow sorting options for API Results
An example of this is the Items/GET API appears to sort the results based on catalog date/item id of the item. It would be nice to specify a different sort parameter that would allow the current sort or a new sort which would return them in the same sorting specified in the Cataloging function in Sierra.
This might be nice for other APIs as well.
5 votesIn 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.
-
Make API loader allow bad MARC
One of the major advantages of Sierra is it's flexibility. Particularly the Sierra fixed fields. Sierra allows those fixed fields to be used in non-standard ways, but the API loader does not have that flexibility. If you try to load records with unexpected data with the API, the load will fail. The API MARC loader does not have to validate MARC. Sierra has never really validated MARC. Don't start now. The API should allow the same weird non-standard data as the rest of Sierra.
7 votesIn 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.
-
Manage Reading History through RESTAPI
Currently patrons can opt in and out of Reading History our public catalog (Bibliocore) but we get many requests from patrons who want to manage that reading history by removing items from Reading History but the RESTAPI doesn't allow users to do that, they have to log into their accounts on WebPac in order to manage the titles in that history. We would like to see full Reading History management currently available in WebPac added to the RESTAPI.
8 votesIn 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.
- Don't see your idea?