Settings and activity
60 results found
-
40 votes
Wes Osborn
supported this idea
·
An error occurred while saving the comment -
23 votes
An error occurred while saving the comment Wes Osborn
commented
This is supported in some 3rd party Discovery Layer products already. It is a shame not to see support for new ILS features show up in Vega first. Vega should be 1st in class in use of underlying ILS features.
Wes Osborn
supported this idea
·
-
36 votesUNDER REVIEW · 3 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Wes Osborn
commented
Deleting them would be tough from a system design perspective, but finding a way to hide them would be great!
Wes Osborn
supported this idea
·
-
34 votesUNDER REVIEW · 5 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
An error occurred while saving the comment Wes Osborn
commented
You might also want to comment on this: https://portal.productboard.com/iii/6-innovative-product-status-board-new/c/932-additional-acquisitions-links-
If needed, you could also use this SQL in the item find tool:
SELECT
DISTINCT cir.ItemRecordID
FROM
Polaris.polaris.PurchaseOrders po WITH (NOLOCK)
JOIN
Polaris.polaris.POLines pol WITH (NOLOCK) ON po.PurchaseOrderID = pol.PurchaseOrderID
JOIN
Polaris.polaris.POLineItemSegments polis WITH (NOLOCK) ON pol.POLineItemID = polis.POLineItemID
JOIN
Polaris.polaris.LineItemSegmentToItemRecord lisir WITH (NOLOCK) ON polis.POLineItemSegmentID = lisir.POLineItemSegmentID
JOIN
Polaris.polaris.CircItemRecords cir WITH (NOLOCK) ON lisir.ItemRecordID = cir.ItemRecordID
WHERE
po.PONumber = 'YourPONumberHere' -
9 votesWes Osborn
supported this idea
·
-
20 votesWes Osborn
supported this idea
·
-
41 votes
An error occurred while saving the comment Wes Osborn
commented
This would be a very big CARROT to the sticks we're typically presenting to members for switching away from the desktop client. If they could quickly switch branches ONLY in Leap that would be a game changer. Even better if they didn't have to pick workstations.
Wes Osborn
supported this idea
·
-
61 votes
An error occurred while saving the comment Wes Osborn
commented
Maybe one way of getting more delivery type information on the receipts would be to have a Printed Name in the branch record. Currently, there is a Display Name, if a Printed Name could be added that would be a helpful place to include the needed delivery/sorting information. That would mirror how InnReach works.
Wes Osborn
supported this idea
·
-
12 votesWes Osborn
shared this idea
·
-
12 votesWes Osborn
supported this idea
·
-
27 votesWes Osborn
supported this idea
·
-
21 votesWes Osborn
shared this idea
·
-
12 votesWes Osborn
supported this idea
·
-
16 votes
An error occurred while saving the comment Wes Osborn
commented
In addition to hampering our ability to move away from the staff client and making us less secure, we also have to find another way to actively prevent people with client admin access from getting to the PolarisSA on the web. There is no separate permission for the web interface. So, if you have access to desktop SA in any form, you have access to Web SA which means you have access to and can manipulate PAPI keys. Which means that even if we don't want people to use it, we can't really prevent them without using another tool/method and still give them access to the desktop client. Those without more sophisticated tooling will then have to forgo the Polaris web SA altogether or risk exposing their API keys to anyone with any level of SA access (even if you preferred they stayed on the desktop).
Wes Osborn
supported this idea
·
An error occurred while saving the comment Wes Osborn
commented
Also, the API key itself shouldn't be visible to ANYONE.
Modern security practice is that you get ONE chance to see the actual key during the creation step and then after that all you can do is disable/delete it.
-
47 votes
An error occurred while saving the comment Wes Osborn
commented
Yes, this is critical to our organizations.
Wes Osborn
supported this idea
·
-
32 votes
An error occurred while saving the comment Wes Osborn
commented
It is wild to think that this date could be updated by anything other than a SQL Update. It shouldn't be exposed in any API or 3rd party integration.
Wes Osborn
supported this idea
·
-
32 votes
An error occurred while saving the comment Wes Osborn
commented
Although we've gotten used to this over the past decade, having this as an option in the ILS would likely greatly improve patron (and staff) satisfaction. Even though would cause some unneeded shipping, which is why having a toggle/setting for it would be nice.
Wes Osborn
supported this idea
·
-
24 votesWes Osborn
supported this idea
·
-
20 votes
An error occurred while saving the comment Wes Osborn
commented
Yes, this would be a time saver for us as well. It would also be nice that if it wasn't going to work that it would provide a better error message. Right now I think it just says system or internal error, something really generic.
Wes Osborn
supported this idea
·
-
13 votes
An error occurred while saving the comment Wes Osborn
commented
This would be SOOOO nice for all date pickers! Or use the OS/browser date picker, which would have this by default.
Wes Osborn
supported this idea
·
Yes, this would be great! And it would help reduce the number of reports that we get saying that an image can't be found or loaded for a particular title.