Settings and activity
153 results found
-
7 votes
Aaron Thomas
shared this idea
·
An error occurred while saving the comment -
3 votes
Aaron Thomas
supported this idea
·
-
17 votes
Aaron Thomas
shared this idea
·
-
16 votes
Aaron Thomas
supported this idea
·
-
5 votes
Aaron Thomas
supported this idea
·
-
18 votes
Aaron Thomas
supported this idea
·
-
20 votes
Aaron Thomas
supported this idea
·
-
11 votes
An error occurred while saving the comment
Aaron Thomas
commented
This would be a great addition for a PAPI to duplicate records. It is possible in Leap and that function works great. A possible GET method would also need to be added to identify duplicate bibs. The addition of both would be amazing for automation tools, etc.
Aaron Thomas
supported this idea
·
-
2 votes
Aaron Thomas
shared this idea
·
-
47 votes
Aaron Thomas
supported this idea
·
-
54 votes
-
11 votes
Aaron Thomas
supported this idea
·
-
38 votes
An error occurred while saving the comment
Aaron Thomas
commented
To Gabrielle's question, no, that process is a separate workflow. An item being declared Lost and Withdrawn are different.
For example, if an item appears on a weeding list but the staff can't find it, why should staff need to check-in the item to either mark as MISSING or Withdrawn?
If an item, for example, is on the shelf but has a ripped cover or missing DVD. Staff will need to mark the item as Withdrawn, not Lost or MISSING. Having to record a check-in first is an added workflow step.
Aaron Thomas
supported this idea
·
-
8 votes
Aaron Thomas
supported this idea
·
-
15 votes
Aaron Thomas
supported this idea
·
-
12 votes
Aaron Thomas
supported this idea
·
-
72 votes
Aaron Thomas
supported this idea
·
-
73 votes
Aaron Thomas
supported this idea
·
-
4 votes
An error occurred while saving the comment
Aaron Thomas
commented
Currently with PAPI there is the ability to GET the contents of a Record Set and PUT additional records into Record Sets. We would love the Record Set API to be fully built out with POST methods (to create new Record Sets) and a DELETE method (to delete an existing Record Set).
Aaron Thomas
shared this idea
·
-
19 votes
Aaron Thomas
supported this idea
·
Polaris 8.1 introduced Bulk Changs within the Request Manager. However, when a bulk change is made, the only verification the user receives is a message that tells the user how many holds were changed. It would be beneficial (and would follow Polaris' bulk change practices) to include the results in the Background Processing function.