Matthew Adair
My feedback
22 results found
-
1 vote
-
5 votes
-
4 votes
-
12 votes
-
28 votes
-
13 votes
An error occurred while saving the comment -
5 votes
-
14 votespartially released ·
AdminKatie Gillespie
(Special Collections & Archives Program Manager, Atlas Systems, Inc.)
responded
Aeon 5.1 added the unlimited custom fields feature but did not increase field sizes.
An error occurred while saving the comment <happy dance> :-)
An error occurred while saving the comment One of the things we ran into when using the shared user database is that each library wanted to track a similar field, but could end up having totally different values for each user, so we needed to move these to UserInfo fields. For example - Status. The 3 libraries wanted to track this separately, it ends up using the the main status field and 2 of the 5 UserInfo fields, so they were used up fast. We ended up having to use a plugin to save the info to a different table, but then the data was not searchable within the Client. Other items that we've been trying to track are "How did you hear about us" "Purpose of today's visit" etc.
I agree with Moira that the Transactions table is just as critical. We're quickly running out of usable fields there, and we've also juggled things around because the default field lengths don't allow us to save the data we need, especially with regards to duplication.
An error occurred while saving the comment I can't tell you how much this would have made our life easier during our implementation phase. This was actually promised during investigation, but it never materialized.
We implemented a shared user database across three sites here on campus, and we all had more information than could be stored in the available fields. We ended up using a plugin to store the info, but it hasn't been very satisfactory.
-
36 votes
-
15 votes
-
8 votes
-
8 votes
An error occurred while saving the comment Granted that everybody's screen sizes are different... In our institution, most staff are using 1920x1280 monitors, and the default window size that the staff client opens to is really quite small.
It would be great if the staff client could remember it's size between sessions, etc.
-
6 votes
-
45 votes
-
18 votes
-
8 votes
-
35 votes
An error occurred while saving the comment I'll second this request (Or maybe third it?) We have the same situation. A user might end up changing locations depending on the kind of materials they are using. Specifically for us, microforms and AV materials.
-
12 votes
-
26 votes
-
8 votes
Another nice option would be the ability to turn off the prompting with the Configuration Manager. Even telling staff not to apply the update themselves, some do and end up messing up their configuration.