Settings and activity
29 results found
-
21 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment 
Ray Voelker
supported this idea
·
-
6 votes
An error occurred while saving the comment Ray Voelker
commented
This really should be considered a bug.
API endpoints can and do go down, so being able to deal with that should be core functionality
Ray Voelker
supported this idea
·
-
25 votes
This enhancement is planned for Sierra 6.6.
Ray Voelker
supported this idea
·
-
13 votesRay Voelker
supported this idea
·
-
3 votesRay Voelker
supported this idea
·
-
21 votes
The product team will review this idea for consideration for a future release.
Ray Voelker
supported this idea
·
An error occurred while saving the comment Ray Voelker
commented
The title of this says all you really need to know about why it'll soon be essential to automate the certificate renewal process ...
"SSL/TLS certificate lifespans reduced to 47 days by 2029"
https://www.bleepingcomputer.com/news/security/ssl-tls-certificate-lifespans-reduced-to-47-days-by-2029/ -
15 votes
An error occurred while saving the comment Ray Voelker
commented
Holds really should be "first class citizens" (e.g. their own set of endpoints, and a proper resource object) when it comes to these REST APIs -- and this is another example of why.
Having the ability to operate directly on a hold (just like any other record) would dramatically improve workflows around holds and open up a lot more possibilities for improved patron service.
Ray Voelker
supported this idea
·
-
23 votesRay Voelker
supported this idea
·
-
23 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Ray Voelker
commented
I'm very much in support of this approach -- adding the stat group to the key to be used as a default value makes it easier for everyone
Ray Voelker
supported this idea
·
-
4 votesRay Voelker
supported this idea
·
-
16 votes
The product team will review this idea for consideration for a future release.
Ray Voelker
supported this idea
·
-
8 votesRay Voelker
supported this idea
·
-
7 votes
The product team will review this idea for consideration for a future release.
Ray Voelker
supported this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
Ray Voelker
supported this idea
·
-
2 votesRay Voelker
supported this idea
·
-
30 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Ray Voelker
commented
@David Jones ... I think that an updated version of Swagger would be a great start, and maybe that's all that's really needed!
Ray Voelker
shared this idea
·
-
6 votesRay Voelker
supported this idea
·
-
21 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Ray Voelker
supported this idea
·
-
5 votes
This idea will be reviewed by the product management team for consideration in an upcoming release.
Ray Voelker
supported this idea
·
-
10 votes
This idea will be reviewed by the product management team for consideration in an upcoming release.
Ray Voelker
supported this idea
·
.png){kind=link}
.png){kind=link}
It would be an amazing resource to have a more "direct" way to retrieve this data on a regular basis for automation and vendor related tasks. It would be nice to have a query parameter to exclude or obfuscate the patron number with this as well.