Erin Nettifee
My feedback
15 results found
-
18 votes
Erin Nettifee supported this idea ·
-
1 vote
Erin Nettifee shared this idea ·
-
1 vote
Erin Nettifee shared this idea ·
-
3 votes
Erin Nettifee supported this idea ·
-
41 votes
Erin Nettifee supported this idea ·
An error occurred while saving the comment -
3 votes
Erin Nettifee shared this idea ·
-
17 votes
Erin Nettifee supported this idea ·
-
1 vote
Erin Nettifee shared this idea ·
-
4 votes
Erin Nettifee supported this idea ·
-
4 votes
Erin Nettifee shared this idea ·
-
228 votes
Erin Nettifee supported this idea ·
An error occurred while saving the comment Erin Nettifee commented
This would be super helpful for Duke which is implementing this year.
-
28 votes
Erin Nettifee shared this idea ·
-
2 votes
Erin Nettifee shared this idea ·
-
80 votes
In order to support this, RESTful APIs to manage the XSL templates would be added to our set of APIs for configuration related entities
An error occurred while saving the comment Erin Nettifee commented
+1 - this would be so helpful. Right now if you want to back up your customizations it is copy and paste.
-
78 votes
An error occurred while saving the comment Erin Nettifee commented
This would solve a major problem for Duke as we implement. The current setup only works well if you are picking up at the owning library. If this was implemented, the solution would be better for all scenarios - picking up at owning library, or picking up at a different library.
Duke would also like this feature. We have patrons with preferred names and would want this to be in place so they are addressed as they want to be called.