Aeon Ideas
12 results found
-
Modify Long Text custom fields to truly be Long Text
The new custom fields are fantastic, with one exception: the Long Text field is still limited to 255 characters.
Ideally, this limit would be removed and the Long Text field would be NVARCHAR(MAX).
At the risk of saying "well, that's easy," having a "LongText NVARCHAR(MAX)" field definition in the CustomFieldValues table seems reasonable enough.
4 votes -
Add key in customization manager to allow automatic user clearance
This should be a yes/no value since many sites have a security process and want to clear users on arrival. But if a site does not want to clear users, this key would automatically set new users (specifically those with SSO credentials affiliated with the institution) to Cleared on registration.
2 votes -
Expand routing rules to use additional tables
Many sites have different workflows for various types of activities. It would be useful to allow routing rules to use the Activity table.
An example would be for Exhibits. These activities often have additional workflow steps and are checked out for longer. It would be useful to use a routing rule to route activity requests for exhibits to custom exhibit queues.
Another example is to narrow the routing to a custom offsite request queue only if requests for a specific activity type should go to the custom queue.
9 votes -
Increase field lengths in LocalInfo table
In the LocalInfo table, SystemName, InstitutionName, and LibraryName are limited to 50 characters. Institutions with multiple sites often wish to combine library names into 1 field or create a system name that is slightly longer. Increasing the character limit to 100 for these fields would provide added flexibility.
2 votes -
Database fields - bigger, better, more flexible
There have been multiple situations that our life would have been made much easier if we had more flexibility in the Aeon database fields. For example, it is often suggested to use "another unused field" to store data. We often run into the issue that these fields are character limited.
The max length of any text field seems to 255 characters, which can be totally impractical for some purposes. I am assuming that this might be because of the MS Word mail merge character limit?
Is there any reason why text fields could not not be expanded to something like…
15 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.
-
Delete users and/or requests
Sites would like to delete users and requests from the database permanently. This is for cleaning up bogus records as well as breaking the connection for old successful requests the site does not want to keep any longer.
6 votes -
Ability to see if a user is signed into the reading room from request grid
We would love a way to see if a user is signed in from the request grids so we can prioritize our paging, etc.
1 vote -
Create compatiblity with Emu (Electronic Museum) database
Create compatibility with Emu (Electronic Museum) database
2 votes -
2 votes
-
Create a description field in the Queues table
There are so many queues, it's good to have a description for their purpose.
8 votes -
1 vote
-
Expand ReferenceNumber field to accommodate the multiple folders listed for a box request
When patrons select multiple folders in the same box, the requests are concatenated into one Aeon Transaction and the folder numbers are placed in the Reference Number field (separated by commas). In theory, this could be as many folders as in a box, but that should be an outlier based on the patron not knowing that they do not need to request each folder.
Currently that field is only 50 characters, so the folders are getting cut off.
Alternately, this information could be put in another field that's larger and more accommodating.
1 vote
- Don't see your idea?