Aeon Ideas
93 results found
-
Update FAQ section on password reset The default text in the FAQ section says:
"In the event that you forget your password, please contact the
Reference staff at (800) 555-1234. We can then reset your password allowing you access to Aeon. Please change your password once you logon to Aeon."For security purposes, patrons should be encouraged to reset their own password. The default language should be updated to direct the patron to ForgotPassword.html first, then to contact staff if they still need assistance.
1 vote -
Show researcher tags associated with activity requests on ViewActivity.html page. Users would like to see tags added to activity requests on the Activity details page.
1 vote -
The ability to use the Site Description column in more areas. Right now the new SiteDescription column offers the ability to create and display more detailed site descriptions, but it is limited to web page grids. It would be nice if this column was opened up for use with other page elements.
1 vote -
Update validation message on Keep in Review page to better indicate which field(s) is not validating. Current Keep in Review validation just says "This request is missing required information." It should be updated to know which field is missing required information so it is more clear to patrons whether they just need to choose a scheduled date or if other required information is missing from a request.
1 vote -
Add integration for requesting from Hyrax UCSC is in the process of creating a new Hyrax based Digital Asset Management System to replace our current system, CONTENTdm. We're at the stage that we're starting to look at implementing Aeon within the new DAMS and would like to option to add a request link to Hyrax. http://hyr.ax/
1 vote -
Clean "Unable to determine StateCode for ID 999" from the Aeon DLL logs There are several places where this message appears. It makes diagnosing other actual errors harder because of the clutter in the logs.
1 vote -
Remove unnecessary tabindex=0 on inputs because they're redundant tabindex=0 adds an html element to the tab order. By default, inputs are already focusable, so they do not need a tabindex=0.
Note: the tabindex=0 should also be removed from any elements that do not explicitly need to be focusable via tab. Screen readers users will be able to reach the text regardless whether it is in the tab order or not. It'll likely just confused keyboard users.
1 vote -
Modify request validation in the web to better support non-transaction fields. - Add RequestLink to Keep in Review form (replace with correct page name)
- In-place request validation should ignore non-transaction fields for Keep in Review page but should consider them when submitting for processing.
1 vote -
Add a link for viewing requests on Aeon's Review Requests page On Aeon's View Requests in Review page, there is no link to view the details of a request. The only options are to either edit individual requests or batch-submit requests.
This can be accomplished by adding one of the following to the Templates/RequestsInReviewDataRow.html page.
<a href="<#DLL queryFields='false'>?Action=10&Form=63&Value=<#DATAROW field='TransactionNumber'>"><#DATAROW field='TransactionNumber'></a>
<a href="<#DLL queryFields='false'>?Action=10&Form=63&Value=<#DATAROW field='TransactionNumber'>">View Request</a>
<a href="<#DLL queryFields='false'>?Action=10&Form=63&Value=<#DATAROW field='TransactionNumber'>">View Request <#DATAROW field='TransactionNumber'></a>1 vote -
Amazon type suggestions for items to request Based off of other items requested and/or research topics
1 vote -
1 vote
-
1 vote
-
1 vote
- Don't see your idea?