Implementing 5.1 Web Page Release Changes

Print Friendly and PDF Follow

The release of Aeon 5.1 comes with several changes to the default web pages. To implement these changes, you can either:

  • Download the 5.1 web pages and replace your existing pages.
  • If you have customizations, find and replace the following code changes mentioned below. Any code highlighted in yellow needs to be removed and any code highlighted in blue needs to be added. 

Important Changes

  • The default RequestsInReviewDataRow.html file was renamed to DataRow_ReviewRequest.html. Code in the default ViewUserReviewRequests.html file was also updated to reflect this change. To ensure that no functionality is broken on your web pages, please either overwrite both files with the new default files or see the Renamed RequestsInReviewDataRow.html section of this guide below to manually make the appropriate changes. 
  • Several of the changes below include extensive changes to atlasUtility.js. In order to ensure that no functionality is broken on your web pages, we recommend overwriting your default atlasUtility.js with the updated file rather than making any changes to this file manually.
If you have any questions, would like to request a copy of your web pages to implement these changes, or require Concierge Services when implementing the new web pages, please contact support at support@atlas-sys.com.

5.1 Release

Appointment Scheduling Web Pages | New Photoduplication Request Pages Custom JavaScript File | Renamed RequestsInReviewDataRow.html | New and Improved Saved Requests Page | Updated Saved Requests Link in Navigation Bar | RequestFor Dropdown for Saved Requests | Web Validation on Saved Requests | HTML5 Form Validation on EAD Requests | Show "FOR DUPLICATION ORDERS" Label on Photoduplication Order Details | Fix Active Request Search Bug | Missing Formnovalidate AttributeUpdated Calendar Icon | Disable Buttons on Form Submission | Changes to Credit Card Pages | Ancillary Data | Footer Tags Added to ViewOrderApprovals.html | Site Map Added to Footer on Logon.html | Normalize Quoting Style for DLL Tags | Removed "form-control" Class from Select Elements | Removed "new-line" Class | Accessibility Updates for Checkboxes and Datarows

Appointment Scheduling Web Pages

New feature-specific appointment scheduling web pages are available to provide patrons with an appointment scheduling interface. The appointment scheduling web pages are not installed by default and must be downloaded from the Aeon Downloads page, manually added to your web directory, and configured to work on your web request forms.

For complete instructions, see Implementing the Appointment Scheduling Web Pages

New Photoduplication Request Pages

These changes were also applied in the v5.0.73 default web pages release.

Two new default web pages have been added for new monograph and archive photoduplication requests along with corresponding edit pages:

  • GenericRequestMonographPhotodup.html
  • GenericRequestManuscriptPhotodup.html
  • EditGenericRequestMonographPhotodup.html
  • EditGenericRequestManuscriptPhotodup.html

To navigate to the new request pages, "Switch to Photoduplication Request" buttons were added to GenericRequestMonograph.html and GenericRequestManuscript.html. Patrons will be able to use these buttons in conjunction with "Switch to Published Materials Request" buttons on the new pages to toggle back and forth between photoduplication and published materials request pages.

Please add EditGenericRequestMonographPhotodup.html and EditGenericRequestManuscriptPhotodup.html to your web directory, and overwrite your default GenericRequestMonograph.html and GenericRequestManuscript.html files with the updated files or make the following changes:

GenericRequestMonograph.html

Add this (default line 32, 34):

<section name="item-info">

<div class="d-flex">
<h3 class="section-header">Item Information</h3>
<div class="ml-auto">
<button id="SwitchToPhotoduplicationRequest" class="btn btn-primary btn-md
switchButton switch-request-form float-right" type="button"
name="switchButton" data-switchrequest-form="20"
data-switchrequest-value="GenericRequestMonographPhotodup">
Switch to Photoduplication Request
</button>
</div>
</div>


<div class="form-group col-md-8">
<label for="ItemTitle">

GenericRequestManuscript.html

Add this (default line 32, 34):

<section name="item-info">

<div class="d-flex">
<h3 class="section-header">Item Information</h3>
<div class="ml-auto">
<button id="SwitchToPhotoduplicationRequest" class="btn btn-primary btn-md
switchButton switch-request-form float-right" type="button"
name="switchButton" data-switchrequest-form="20"
data-switchrequest-value="GenericRequestManuscriptPhotodup">
Switch to Photoduplication Request
</button>
</div>
</div>


<div class="form-group col-md-8">
<label for="ItemTitle">

Custom JavaScript File

These changes were also applied in the v5.0.73 default web pages release.

A blank custom.js file was added to the default web pages for site-specific custom JavaScript changes. To use the new file for your custom JavaScript changes, please add custom.js to your web directory in the "js" folder, and overwrite your default include_head.html file with the updated file or make the following changes:

include_head.html

Add this (default line 21):

<script src="js/atlasUtility.js"></script>
<script src="js/custom.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.22.2/moment-with-locales.min.js"
integrity="sha256-VrmtNHAdGzjNsUNtWYG55xxE9xDTz4gF63x/prKXKH0=" crossorigin="anonymous"></script>

Renamed RequestsInReviewDataRow.html

The default RequestsInReviewDataRow.html file was renamed to DataRow_ReviewRequest.html. This change also affects code on the default ViewUserReviewRequests.html page. There are two options to implement this change:

  1. Overwrite your default RequestsInReviewDataRow.html file with the new DataRow_ReviewRequest.html file, and overwrite your default ViewUserReviewRequests.html with the new default file.
  2. Manually change the name of RequestsInReviewDataRow.html file to DataRow_ReviewRequest.html (or overwrite it with the new, renamed file), and then manually make the following change on ViewUserReviewRequests.html:

ViewUserReviewRequests.html

Change this (default lines 30-32):

<div id="saved-requests">
<#DATAREPEATER Name="RequestsInReview"
TemplateFile="Templates\RequestsInReviewDataRow.html"
NoDataAction="<div class='no-data-message'>
You do not currently have any requests in review</div>">
</div>
 

To this:

<div id="saved-requests">
<#DATAREPEATER Name="RequestsInReview"
TemplateFile="Templates\DataRow_ReviewRequest.html"
NoDataAction="<div class='no-data-message'>
You do not currently have any requests in review</div>">
</div>

New and Improved Saved Requests Page

SavedRequestsButtons.png

RequestsInReviewDataRow.html (renamed DataRow_ReviewRequest.html) was updated to display new features and options on the "Saved Requests" web page. The following additions were made:

  • Item titles now link to their associated request detail pages.
  • Edit and Request Copy buttons are now visible by default for each request.
  • An Actions dropdown menu was added with Cancel, Clone to Copy, Export Citation, and Submit Request options available depending on the state of the request.

To implement these changes, please overwrite RequestsInReviewDataRow.html with the new DataRow_ReviewRequest.html file, or make the following changes to your original RequestsInReviewDataRow.html file:

RequestsInReviewDataRow.html

Link Item Title to Request Details

Change this (default line 14):

 
 
<#DATAROW field="ItemTitle"> 
 

To this:

<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">

<#DATAROW field="ItemTitle"></a>

Add New Buttons and Actions Menu

Change this (default lines 9-12):

<div class="col-sm-6 col-lg-2 order-lg-last text-right">
<a class="btn btn-primary menuEdit
<#DATAROW field='RequestActionAllowed' name='Edit'
disabledValue='disabled'>" href="<#DLL queryFields='false'>
?Action=20&Value=<#DATAROW field='TransactionNumber'>">
<span span aria-hidden="true" class="far fa-edit mr-1">
</span>Edit</a>
</div>
<div class="col-sm-12 col-lg-9 table-data-row-details">
<h4 class="card-title">
 

To this:

 
 
 
 
 
 
 
 

<div class="col-lg-4 col-md-12">
<h4 class="card-title">

Change this (default lines 16-20):

<h5 class="card-subtitle mb2 text-muted">
<#DATAROW field='ItemSubtitle'></h5>
<div class="field text-muted">Transaction Number
<span class="field-value font-weight-bold ml-1">
<#DATAROW field='TransactionNumber'>
</span></div>

</div>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

</div>
 

To this:

<h5 class="card-subtitle   text-muted">
<#DATAROW field="ItemSubtitle"></h5>
 
 
 
 

</div>
<div class="col-lg-7 col-md-12 text-right">
<a class="btn btn-primary <#DATAROW field='RequestActionAllowed'
name='Edit' disabledValue='disabled'>"
href="<#DLL queryFields='false'>?Action=20&amp;
Value=<#DATAROW field='TransactionNumber'>"
class="menuEdit"><span span aria-hidden="true"
class="far fa-edit">
</span> Edit</a>

<a class="btn btn-primary <#DATAROW field='RequestActionAllowed'
name='RequestCopy' disabledValue='disabled'>"
href="<#DLL queryFields='false'>?Action=20&Form=34&amp;Value=
<#DATAROW field='TransactionNumber'>" class="menuEdit">
<span span aria-hidden="true" class="fas fa-copy">
</span> Request Copy</a>

<div class="btn-group" role="group">
<button id="btnGroupDrop<#DATAROW field='TransactionNumber'>"
type="button" class="btn btn-secondary dropdown-toggle"
data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
Actions
</button>
<div class="dropdown-menu"
aria-labelledby="btnGroupDrop<#DATAROW field='TransactionNumber'>">
<a class="dropdown-item btn btn-light
menuClone <#DATAROW field='RequestActionAllowed'
name='Cancel' disabledValue='d-none'>"
href="aeon.dll?Action=21&amp;Type=10&amp;Value=
<#DATAROW field='TransactionNumber'>"><span aria-hidden="true"
class="fas fa-ban text-danger"></span> Cancel Request</a>
<a class="dropdown-item btn btn-light
menuPhotoduplication <#DATAROW field='RequestActionAllowed'
name='CloneToCopy' disabledValue='d-none'>"
href="aeon.dll?Action=11&amp;Form=33&amp;Value=<
#DATAROW field='TransactionNumber'>"><span aria-hidden="true"
class="fas fa-cart-plus text-primary"></span> Clone to Copy</a>
<a class="dropdown-item btn btn-light
menuExportRIS <#DATAROW field='RequestActionAllowed'
name='ExportRIS' disabledValue='d-none'>"
href="aeon.dll?Action=10&amp;Form=121&amp;Value=
<#DATAROW field='TransactionNumber'>"><span aria-hidden="true"
class="fas fa-download text-primary"></span> Export Citation</a>
<a class="dropdown-item btn btn-light
menuPhotoduplication <#DATAROW field='RequestActionAllowed'
name='Submit' disabledValue='d-none'>"
href="aeon.dll?Action=23&amp;Type=12&amp;Value=
<#DATAROW field='TransactionNumber'>"><span aria-hidden="true"
class="fas fa-share-square"></span> Submit Request</a>
</div>
</div>
</div>

</div>

Updated Saved Requests Link in the Navigation Bar

SavedRequestsNavMenu.png

The Saved Requests link in the navigation bar's Order History dropdown menu was updated with new functionality to display the user's current number of saved requests to its right and a shopping cart icon to its left. To implement this change, please overwrite your default include_nav.html file with the updated file or make the following changes:

include_nav.html

Change this (default lines 32-36):

<a class="nav-link dropdown-toggle" href="#" 
id="navbarOrderHistory" data-toggle="dropdown"
aria-haspopup="true" aria-expanded="false">
<span aria-hidden="true" class="fas fa-history">
</span> Order History</a>
<div class="dropdown-menu"
aria-labelledby="navbarOrderHistory">
<a class="dropdown-item"
href="<#ACTION action='10' form='76'>">
 
 
 
Saved Requests</a>

<a class="dropdown-item"
href="<#ACTION action='10' form='62'>">
Outstanding Requests</a>
 

To this:

<a class="nav-link dropdown-toggle" href="#" 
id="navbarOrderHistory" data-toggle="dropdown"
aria-haspopup="true" aria-expanded="false">
<span aria-hidden="true" class="fas fa-history">
</span> Order History</a>
<div class="dropdown-menu"
aria-labelledby="navbarOrderHistory">
<a class="dropdown-item"
href="<#ACTION action='10' form='76'>">
<span aria-hidden="true" class="fas fa-shopping-cart">
</span> Saved Requests
<span class="badge badge-primary badge-pill ">
<#USER field="UserReviewCount"></span></a>

<a class="dropdown-item"
href="<#ACTION action='10' form='62'>">
Outstanding Requests</a>

RequestFor Dropdown for Saved Requests

Added a RequestFor dropdown on ViewUserReviewRequests.html so that saved requests can now be associated with a researcher or activity when submitted. Please overwrite your default ViewUserReviewRequests.html file with the updated file or make the following changes:

ViewUserReviewRequests.html 

Add this (default line 47):

<div id="request-link-div" class="form-group visit-date col-md-5 
<#PARAM name='RequestLinksVisible' enabled='RequestForEnabled' disabled='d-none'>">
<label for="RequestLink">
<span class="<#ERROR name='ERRORRequestLink'>">
Request for
</span>
</label>
<select class="custom-select mr-sm-2" id="RequestLink" name="RequestLink" size="1" >
<#OPTION name="RequestLinks" hideUsernames="true">
</select>
</div>

Change this (default lines 48-58):


<script>
   $(document).ready(function () {
        if (($('#saved-requests .card').length == 0)) {
            $('#scheduled-date-div').hide();
                                          
        }
        else
        {
            $('#scheduled-date-div').show();
                                         
        }
   });
</script>
 

To this:


<script>
   $(document).ready(function () {
        if (($('#saved-requests .card').length == 0)) {
            $('#scheduled-date-div').hide();
            $('#request-link-div').hide();
        }
        else
        {
            $('#scheduled-date-div').show();
            $('#request-link-div').show();
        }
   });
</script>

Web Validation on Saved Requests

To fix an issue where web validation is not applied to saved requests, please overwrite your default KeepInReview.js file with the updated file or make the following change:

KeepInReview.js

Change this (default lines 26, 109):

statusRoot = $('#status');
 

To this:

statusRoot = $('#statusLine');

HTML5 Form Validation on EAD Requests

These changes were also applied in the v5.0.73 default web pages release.

The EAD request form was updated to apply HTML5 validation on fields, for example when validating input on required fields. To apply this change, please overwrite your default EADRequest.html file with the updated file or make the following change:

EADRequest.html

Change this (default lines 18-19):

   $(':submit').click(function (event) { SubmitEADForm(this, event); return false; });
});

To this:

    $(':submit').click(function (event) { 
if ($(this).closest("form").get(0).reportValidity()) {
SubmitEADForm(this, event);
}
return false;
});

Show "FOR DUPLICATION ORDERS" Label on Photoduplication Order Details

These changes were also applied in the v5.0.73 default web pages release.

DuplicationLabel.png

To fix an issue where the "FOR DUPLICATION ORDERS" label was hidden on the detailed information page for photoduplication orders, please overwrite your default ViewDetailedDefaultInformation.html file with the updated file or make the following change:

ViewDetailedDefaultInformation.html

Change this (default lines 150-155):

<div class="field list-group-item             
 
">
<div class="d-flex justify-content-between">
<span class="transaction-label">
FOR DUPLICATION ORDERS:</span>
<span class="field-value"></span>
</div>
</div>
 

To this:

<div class=" list-group-item <#TRANSACTION display='CheckHasValue' 
field='PhotoduplicationQueueName' disabledValue='d-none'>
">
<div class="d-flex justify-content-between">
<span class="transaction-label">
FOR DUPLICATION ORDERS:</span>
</div>
</div>

Fix Active Request Search Bug

These changes were also applied in the v5.0.73 default web pages release.

To fix an issue where the "Search only active requests" option returns results for all requests, we recommend overwriting your default atlasUtility.js and ViewSearchResults.html files with the updated files due to extensive changes made in atlasUtility.js. Alternatively, you can overwrite the default atlasUtility.js file and then make the following changes manually to ViewSearchResults.html:

atlasUtility.js

The changes to this file are extensive. Please overwrite this file with the updated file.

ViewSearchResults.html

Change this (default lines 18-32):

<form action="aeon.dll" name="Search" method="post">
<input type="hidden" name="AeonForm" value="Search">
<input id="SessionID" name="SessionID" type="hidden"
value="<#PARAM name='SessionID'>">

<input id="SearchCriteria" value="<#PARAM name='SearchCriteria'>"
name="SearchCriteria" type="text" title="Search criteria">
<form class="form-inline my-1 my-lg-0">
<input class="btn btn-primary btn-sm" type="submit"
name="SubmitButton" value="Search" title="Search"
 >
</form>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
<div id="searchType">
<input checked name="SearchType" type="radio"
id="SearchTypeActive" value="Active"
 >
<label for="SearchTypeActive"><span>Search <u>only</u>
active requests</span></label>

<input class="ml-3" name="SearchType" type="radio"
id="SearchTypeAll" value="All"
 >
<label for="SearchTypeAll">Search all requests</label>
</div>
</form>
 

To this:

<form action="aeon.dll" name="Search" method="post">
<input type="hidden" name="AeonForm" value="Search">
 
 
<input id="SearchCriteria" value="<#PARAM name='SearchCriteria'>"
name="SearchCriteria" type="text" title="Search criteria">
 
<input class="btn btn-primary btn-sm" type="submit"
name="SubmitButton" value="Search" title="Search"
data-button-nodisable>
 
<!--Switch control for search filtering-->
<!--
<div class="custom-control custom-switch" id="customSearchType">
<input type="checkbox" name="SearchType"
class="custom-control-input"
id="SearchType" value="Active"
data-persisted-value="<#PARAM name='SearchType'>">
<label class="custom-control-label" for="SearchType">
Search <u>only</u> active requests</label>
</div>
-->

<!--Radio control for search filtering-->
<br>
 
<div id="searchType">
<input checked name="SearchType" type="radio"
id="SearchTypeActive" value="Active"
data-persisted-value="<#PARAM name='SearchType'>">
<label for="SearchTypeActive"><span>Search <u>only</u>
active requests</span></label>

<input class="ml-3" name="SearchType" type="radio"
id="SearchTypeAll" value="All"
data-persisted-value="<#PARAM name='SearchType'>">
<label for="SearchTypeAll">Search all requests</label>
</div>
</form>

Missing Formnovalidate Attribute

These changes were also applied in the v5.0.73 default web pages release.

A previously missing "formnovalidate" attribute was added to the cancel button on ExpiredUsers.html in order to allow users to stop the request form and return to the main menu. To fix this issue, please overwrite your default ExpiredUsers.html file with the updated file or make the following change:

ExpiredUsers.html

Change this (default line 297):

<button class="btn btn-secondary btn-md" type="submit" 
name="SubmitButton" value="Cancel - Exit to Main Menu" >
Cancel - Exit to Main Menu</button>
 

To this:

<button class="btn btn-secondary btn-md" type="submit" 
name="SubmitButton" value="Cancel - Exit to Main Menu" formnovalidate>
Cancel - Exit to Main Menu</button>

Updated Calendar Icon

NewCalendarIcon.png

The calendar icon next to the date picker on request forms has been updated with a new look as a clickable "Font Awesome" icon. To implement this change, please overwrite the following default files with the new files or make the specified changes to each file listed below:

  • atlasUtility.js
  • scheduled-date.js
  • DefaultRequest.html
  • EADRequest.html
  • EditDefaultRequest.html
  • EditEADRequest.html
  • EditGenericRequestManuscript.html
  • EditGenericRequestMonograph.html
  • EditGenericRequestSerial.html
  • GenericRequestManuscript.html
  • GenericRequestMonograph.html
  • GenericRequestSerial.html
  • ViewUserReviewRequests.html

atlasUtility.js

The changes to this file are extensive. Please overwrite this file with the updated file.

scheduled-date.js

Change this (default lines 173-178):

buttonImage: "css/images/cal_24x24.png",
buttonImageOnly: true,
showOn: "button",

onChangeMonthYear: function(){
setTimeout(function(){
changeDisableDateColor();
 

To this:

 
 
 
onChangeMonthYear: function(){
setTimeout(function(){
changeDisableDateColor();

Request Forms

Change this:

<div class="input-group">
<input class="form-control" id="ScheduledDate"
name="ScheduledDate" type="textbox"
value="<#PARAM name='ScheduledDate'>">
 
 
 
 
 
 
 
 
 

</div>
 

To this:

<div class="input-group">
<input class="form-control" id="ScheduledDate"
name="ScheduledDate" type="text"
aria-describedby="button-datePicker-scheduledDate"
value="<#PARAM name='ScheduledDate'>">
<div class="input-group-append">
<button class="btn btn-outline-secondary dateTrigger"
type="button" role="button"
id="button-datePicker-scheduledDate"
data-triggerDatePicker="#ScheduledDate" aria-label="Calendar">
<span class="fas fa-calendar ui-datepicker-trigger"></span>
</button>
</div>

</div>

On these web pages:

  • DefaultRequest.html (default lines 172-174)
  • EADRequest.html (default lines 101-103)
  • EditDefaultRequest.html (default lines 181-183)
  • EditEADRequest.html (default lines 148-150)
  • EditGenericRequestManuscript.html (default lines 133-135)
  • EditGenericRequestMonograph.html (default lines 188-190)
  • EditGenericRequestSerial.html (default lines 172-174)
  • GenericRequestManuscript.html (default lines 139-141)
  • GenericRequestMonograph.html (default lines 176-178)
  • GenericRequestSerial.html (default lines 144-146)
  • ViewUserReviewRequests.html (default lines 40-42)

Disable Buttons on Form Submission

These changes were also applied in the v5.0.73 default web pages release.

atlasUtility.js was updated with new functionality that disables most buttons while submitting a form. This functionality protects against duplicate form submissions caused by clicking the form submit button twice and also prevents a user from navigating away from the page in the middle of a form submission, eliminating any confusion as to whether or not the submission went through.

This change applies to any button element that is type "submit" unless that button element also contains the data attribute "data-button-nodisable," which will disable the new functionality. To accomodate these changes, the Search button was also updated with new code on ViewSearchResults.html.

To implement these changes, please overwrite your default atlasUtility.js and EADRequest.js with the updated files and either overwrite your default ViewSearchResults.html with the updated file or make the following changes:

atlasUtility.js

The changes to this file are extensive. Please overwrite this file with the updated file.

EADRequest.js

Please overwrite this file with the updated file.

ViewSearchResults.html

Change this (default line 23):

<input class="btn btn-primary btn-sm" 
type="submit" name="SubmitButton" value="Search"
title="Search">
 

To this:

<button class="btn btn-primary btn-sm" 
type="submit" name="SubmitButton" value="Search"
title="Search" data-button-nodisable>Search</button>

Changes to Credit Card Payment Pages

These changes were also applied in the v5.0.73 default web pages release.

Significant changes have been made to the credit card payment pages to improve their functionality. Please review the changes listed below and make the recommended updates to your payment pages.

Note: The following changes are significant. To implement these changes, please move your web customizations to the new files and overwrite your existing CreditCardPayment.html file with the updated default file following the instructions below.

New Default Payment Pages

The credit card payment pages are no longer feature-specific pages and have been added to the default web pages with a few significant changes:

  • CreditCardPayment.html is now a single default file instead of a separate file for each payment provider.
  • Specific payment providers are configured on CreditCardPayment.html through newly added include files for each payment provider. These files follow the naming scheme include_payment_form_[PaymentProviderName].html and are located in a new "payments" subfolder found in the "templates" folder in the web directory.
  • An include_payment_form_none.html file was added to act as a default placeholder on CreditCardPayment.html.
  • Payment buttons for each payment provider page have been broken out into an include_payment_buttons.html file located in the "payments" subfolder found in the "templates" folder in the web directory.
  • A CreditCardPaymentConfirmation.html default file has been added for TouchNet, as well as include_confirmation_form_none.html and include_confirmation_form_touchnet.html pages (see Configuring Additional TouchNet Pages below).

Exception for Sage Pay Payment Gateway

Sage Pay will not use the new default CreditCardPayment.html file and will instead use a feature-specific CreditCardPayment.html. As such, an include_payment_form file is not included for Sage Pay. Please follow the Sage Pay-specific instructions below when implementing the new pages for this payment gateway.

Complete list of new default include files:

  • include_confirmation_form_none.html
  • include_confirmation_form_touchnet.html
  • include_payment_buttons.html
  • include_payment_form_authorize.net.html
  • include_payment_form_authorize.net_accept_hosted.html
  • include_payment_form_cybersource.html
  • include_payment_form_none.html
  • include_payment_form_payeezy.html
  • include_payment_form_paypal.html
  • include_payment_form_touchnet.html

Migrating Your Payment Page Web Customizations

Web customizations or configurations that were previously made on the feature-specific CreditCardPayment.html file for your payment provider will need to be migrated to the new include_payment_form_[PaymentProviderName].html file for your provider. These configurations can be applied to the new file in the same manner that they were made in your original CreditCardPayment.html file.

Migrating Sage Pay Payment Page Web Customizations

As Sage Pay will not use an include_payment_form include file, any customizations on your original CreditCardPayment.html should be migrated to the new feature-specific CreditCardPayment.html Sage Pay file.

Additional TouchNet Customizations

The Upay and T-Link URLs for TouchNet are configured on lines 1 and 20 of include_payment_form_touchnet.html. These should set on the new include file according to the same configurations used on your previous TouchNet-specific CreditCardPayment.html file.

Configuring the New Pages

To configure the new CreditCardPayment.html file for your specific payment provider, follow these steps:

  1. Download the new default web pages.
  2. From the default web page download, navigate into the "templates" folder. Add the new "payment" subfolder to your web directory in the "templates" folder (default location: C:\Program Files (x86)\Aeon\Web\templates).
  3. Add any web edits/configurations you had made on your original CreditCardPayment.html file to the new include_payment_form_[PaymentProviderName].html file. 
  4. Overwrite CreditCardPayment.html with the updated file in your web directory (default location: C:\Program Files (x86)\Aeon\Web). 
  5. Replace the default placeholder include file with your payment provider's include file on line 42 of CreditCardPayment.html as follows:

CreditCardPayment.html

Change this (default line 42):

<#INCLUDE filename=
"templates/payment/include_payment_form_none.html">
 

To this:

<#INCLUDE filename=
"templates/payment/include_payment_form_[PaymentProviderName].html">

Configuring Additional TouchNet Pages

After following the steps above, an additional CreditCardPaymentConfirmation.html file must be configured for the TouchNet gateway following these steps:

  1. Add any web edits/configurations you had made on your original CreditCardPaymentConfirmation.html file to the new include_payment_confirmation_form_touchnet.html file. 
  2. Overwrite CreditCardPaymentConfirmation.html with the updated file in your web directory (default location: C:\Program Files (x86)\Aeon\Web). 
  3. Replace the default placeholder include file with your payment provider's include file on line 13 of CreditCardPaymentConfirmation.html as follows:

CreditCardPaymentConfirmation.html

Change this (default line 13):

<#include filename=
"templates/payment/include_confirmation_form_none.html">
 

To this:

<#include filename=
"templates/payment/include_confirmation_form_touchnet.html">

Configuring the Sage Pay Pages

To configure the new CreditCardPayment.html file for Sage Pay, follow these steps:

  1. Download the new default web pages.
  2. Download the feature-specific CreditCardPayment.html for Sage Pay.
  3. From the default web page download in step one, navigate into the "templates" folder. Add the new "payment" subfolder to your web directory in the "templates" folder (default location: C:\Program Files (x86)\Aeon\Web\templates).
  4. Add any web edits/configurations you had made on your original CreditCardPayment.html file to the new CreditCardPayment.html file downloaded in step two.
  5. Overwrite CreditCardPayment.html with the updated file in your web directory (default location: C:\Program Files (x86)\Aeon\Web). 

Ancillary Data

These changes were also applied in the v5.0.73 default web pages release.

Several updates were made to the handling for the 'ancillaryData' TouchNet fields to address a bug that prevented data from passing correctly to TouchNet. Please make updates to the following web pages to fix this issue:

CreditCardPayment.html/include_payment_form_touchnet.html

An 'ancillaryData' field must be added to the ajax data section in CreditCardPayment.html or in include_payment_form_touchnet.html if you have updated to the new default credit card payment pages (see Changes to Credit Card Payment Pages above). Any Aeon field can be passed to the 'ancillaryData' property in order to submit that information as ancillary data.

For example, to submit a payment's transaction numbers as ancillary data, you would add the following line:

errorLink: "<#CUSTOMIZATION name='WebURL'>aeon.dll?action=30&type=113",
cancelLink: "<#CUSTOMIZATION name='WebURL'>aeon.dll?action=30&type=104",
ancillaryData: "<#PARAM name='TransactionNumbers'>"

CreditCardPaymentConfirmation.html

The "AncillaryData" hidden input should be removed from CreditCardPaymentConfirmation.html if previously added, as there is no longer a need for the ancillary data parameter on this page. A payment's ancillary data is now stored in the BillingGatewayTransactions table in the CustomData field and is sent to TouchNet when completing the payment.  

Remove the following line:

<input type="hidden" name="AncillaryData" value="<#PARAM name=
"AncillaryData">">

Footer Tags Added to ViewOrderApprovals.html

These changes were also applied in the v5.0.73 default web pages release.

Footer tags have been added to the default ViewOrderApprovals.html file. To implement these changes, please overwrite your default ViewOrderApprovals.html file with the updated file or make the following changes:

ViewOrderApprovals.html

Change this (default line 59):

 
<#INCLUDE filename="include_footer.html">
 
 

To this:

<footer>
<#INCLUDE filename="include_footer.html">
</footer>

Site Map Added to Footer on Logon.html

These changes were also applied in the v5.0.73 default web pages release.

A link to the Site Map was added to the footer on the default logon page. To implement these changes, please overwrite your default Logon.html file with the updated file or make the following changes:

Logon.html

Change this (default lines 74-77):

<footer class="foot">
<div>Powered by Aeon</div>
<div> &copy; 2021 <a href="http://www.atlas-sys.com">
Atlas Systems, Inc.</a> All Rights Reserved.</div>
 
 
 
</footer>
 

To this:

<footer class="foot">
<div>Powered by Aeon</div>
<div> &copy; 2021 <a href="http://www.atlas-sys.com">
Atlas Systems, Inc.</a> All Rights Reserved.</div>
<div>
<a href="aeon.dll?Action=10&Form=3">Site Map</a>
</div>

</footer>

Normalize Quoting Style for DLL Tags

This change impacts a large number of web pages. To implement this change, please overwrite your default web pages with the updated files or make the changes manually on each page following the example below.

The quoting style for DLL tags (tags that begin "<#") was changed to use double-quotes for attributes wherever these tags were not already nested within double-quotes. An example of this change is in DataRow_DefaultRequest.html (this page will also require additional changes):

DataRow_DefaultRequest.html

Change this:

<span id="Tooltip_ItemStatus_
<#DATAROW field='TransactionNumber'>"
class="d-none" role="tooltip">
Moved to <#DATAROW field='TransactionStatus'>
on <span class="convert-local" data-iso8601="
<#DATAROW field='TransactionDate' display='ISO8601'>">
<#DATAROW field='TransactionDate'></span>
</span>
 

To this:

<span id="Tooltip_ItemStatus_
<#DATAROW field='TransactionNumber'>"
class="d-none" role="tooltip">
Moved to <#DATAROW field="TransactionStatus">
on <span class="convert-local" data-iso8601="
<#DATAROW field='TransactionDate' display='ISO8601'>">
<#DATAROW field="TransactionDate"></span>
</span>

Explanation:

  • <#DATAROW field='TransactionNumber'> and the first instance of<#DATAROW field='TransactionDate'> use single quotes around the attribute because the tags are inside the double-quotes of the "id" and "data-iso8601" attributes respectively.
  • <#DATAROW field='TransactionStatus'> and the second instance of <#DATAROW field='TransactionDate'> must be changed to <#DATAROW field="TransactionStatus"> and <#DATAROW field="TransactionDate"> since these tags are not already nested within double-quotes.

Please follow the example above to make this change on these web pages:

  • DataRow_BillingData.html 
  • DataRow_CreditCardOrder.html 
  • DataRow_DefaultActivity.html 
  • DataRow_DefaultNote.html 
  • DataRow_DefaultRequest.html 
  • DataRow_ElectronicDelivery.html 
  • DataRow_OrderBilling.html 
  • DataRow_OrderEstimate.html 
  • RequestsInReviewDataRow.html 
  • ActivityInformation.html 
  • ChangeUserInformation.html 
  • DefaultRequest.html 
  • DetailedInformation.html 
  • EADRequest.html 
  • EditDefaultRequest.html 
  • EditEADRequest.html
  • EditGenericRequestManuscript.html 
  • EditGenericRequestManuscriptPhotodup.html 
  • EditGenericRequestMonograph.html 
  • EditGenericRequestMonographPhotodup.html
  • EditGenericRequestSerial.html 
  • EditPhotoduplicationRequest.html
  • ExpiredUsers.html 
  • GenericRequestManuscript.html 
  • GenericRequestManuscriptPhotodup.html
  • GenericRequestMonograph.html 
  • GenericRequestMongraphPhotdup.html 
  • GenericRequestSerial.html 
  • include_nav.html 
  • include_photoduplication.html 
  • include_ResearcherTagsUpdate.html
  • include_scheduleddate_review_toggle.html 
  • NewAuthRegistration.html 
  • NewUserRegistration.html 
  • PhotoduplicationRequest.html
  • ViewCancelledDetailedInformation.html 
  • ViewDefaultDetailed.html 
  • ViewDetailedDefaultInformation.html 
  • ViewDetailedInformation.html 
  • ViewDetailedManuscriptInformation.html 
  • ViewDetailedMongraphInformation.html 
  • ViewDetailedSerialInformation.html 
  • ViewRequestsByTag.html 
  • ViewSearchResults.html 

Removed "form-control" Class from Select Elements

This change impacts a large number of web pages. To implement this change, please overwrite your default web pages with the updated files or make the changes manually on each page following the example below.

The "form-control" class was removed from all select elements, including select elements where it was incorrectly added as a second class attribute at the end of the tag. An example of this change is in DefaultRequest.html:

DefaultRequest.html

Change this:

<select class="form-control custom-select mr-sm-2" 
id="RequestLink" name="RequestLink" size="1">
<#OPTION name="RequestLinks">
</select>
 

To this:

<select class="custom-select mr-sm-2" 
id="RequestLink" name="RequestLink" size="1">
<#OPTION name="RequestLinks">
</select>

Please follow the example above to make this change on these web pages:

  • DefaultRequest.html
  • EADRequest.html 
  • EditDefaultRequest.html 
  • EditEADRequest.html
  • EditGenericRequestManuscript.html 
  • EditGenericRequestManuscriptPhotodup.html 
  • EditGenericRequestMonograph.html
  • EditGenericRequestMonographPhotodup.html 
  • EditGenericRequestSerial.html

  • EditPhotoduplicationRequest.html
  • GenericRequestManuscript.html
  • GenericRequestManuscriptPhotodup.html
  • GenericRequestMonograph.html
  • GenericRequestMongraphPhotdup.html
  • GenericRequestSerial.html 
  • include_photoduplication.html 
  • PhotoduplicationRequest.html

Removed "new-line" Class

These changes were also applied in the v5.0.73 default web pages release.

The "new-line" class was removed from aeon.css and all <span> elements using the "new-line" class attribute were replaced with <div> elements. To implement this change, please overwrite the default web pages listed below with the updated files, or make the following changes manually to each page:

Remove the "new-line" class on aeon.css:

aeon.css

Change this (default lines 118-127):

 padding: 1rem 0;
}
.new-line {
display: block;
}
.bold {
font-weight: bold;
}
 

To this:

 padding: 1rem 0;
}
 
 
 
.bold {
font-weight: bold;
}

Replace <span class="new-line"> with <div> tags following the example below:

FAQ.html

Change this (default lines 115-128):

<h2>Who do I contact if I have problems with or 
questions about Aeon?</h2>

<p>
<span class="new-line">
System Problems or Questions: Special Collections
office at (800) 555-1212 or email to
<a href="mailto:contactus@youruniversity.edu">
contactus@youruniversity.edu</a>
</span>
<span class="new-line">
Technical Support Questions: Email anytime to
<a href="mailto:contactus@youruniversity.edu">
contactus@youruniversity.edu</a>
</span>
</p>

<a name="cookie"></a>
 

To this:

<h2>Who do I contact if I have problems with or 
questions about Aeon?</h2>

 
<div>
System Problems or Questions: Special Collections
office at (800) 555-1212 or email to
<a href="mailto:contactus@youruniversity.edu">
contactus@youruniversity.edu</a>
</div>
<div>
Technical Support Questions: Email anytime to
<a href="mailto:contactus@youruniversity.edu">
contactus@youruniversity.edu</a>
</div>
 

<a name="cookie"></a>

Please follow the example above to make this change on these web pages:

  • ExpiredUsers.html (default lines 264-270)
  • FirstTime.html (default lines 32-38)
  • include_footer.html (default lines 2-11)
  • Logon.html (default lines 41-46; 79-82)
  • Logon2.html (default lines 28-29)
  • NewAuthRegistration (default lines 20-25)

Make the following changes to replace the "new-line" class with additional formatting on these web pages:

AboutAeon.html

Change this (default lines 10-22):

<div class="container">
<p>
<span class="new-line">
Aeon is special collections circulation
and workflow automation software for special
collections libraries designed by special
collections librarians.
</span>
<span class="new-line">
Aeon improves customer service and staff efficiency
while providing unparalleled item tracking,
security, and statistics.
</span>
</p>

<#INCLUDE filename="include_footer.html">
 

To this:

<div class="container">

<div class="mt-5 mb-3">
Aeon is special collections circulation
and workflow automation software for special
collections libraries designed by special
collections librarians.
</div>
<div class="mt-3 mb-5">
Aeon improves customer service and staff efficiency
while providing unparalleled item tracking,
security, and statistics.
</div>
 

<#INCLUDE filename="include_footer.html">

ExpiredUsers.html

Change this (default lines 21-29):

<div id="statusLine"><#STATUS></div>
<p>
<span class="new-line">
Your account has expired. Accounts expire
once per year. Please confirm or update your
information below and click the
'Submit Information' button to continue.
</span>
</p>

<section name="user-info">
 

To this:

<div id="statusLine"><#STATUS></div>
 
<div class="mt-3 mb-3">
Your account has expired. Accounts expire
once per year. Please confirm or update your
information below and click the
'Submit Information' button to continue.
</div>
 

<section name="user-info">

FirstTime.html

Change this (default lines 55-69):

<p>
<strong class="new-line">Username</strong>
<span class="new-line">
Choose anything you like, such as your name,
abbreviations, or an alphanumeric code.
</span>

<strong class="new-line">Password</strong>
<span class="new-line">
Choose anything you like. We recommend that you follow
good security practice and choose a password
that is different from those you use to access other systems.
</span>
<span class="new-line">
Aeon will encrypt your password, so it will remain secure.
Only you will know your password.
</span>
</p>
 

To this:

<div>
<strong >Username</strong>
<div>
Choose anything you like, such as your name,
abbreviations, or an alphanumeric code.
</div>

<strong >Password</strong>
<div>
Choose anything you like. We recommend that you follow
good security practice and choose a password
that is different from those you use to access other systems.
</div>
<div>
Aeon will encrypt your password, so it will remain secure.
Only you will know your password.
</div>
</div>

ViewSearchResults.html

Change this (default lines 24-32):

<div id="searchType">

<input checked name="SearchType" type="radio"
id="SearchTypeActive" value="Active">
<label for="SearchTypeActive">
<span class="new-line">Search <u>only</u> active requests</span>
</label>
<input   name="SearchType" type="radio"
id="SearchTypeAll" value="All">
<label for="SearchTypeAll">Search all requests</label>
</div>
 

To this:

<div id="searchType">

<input checked name="SearchType" type="radio"
id="SearchTypeActive" value="Active">
<label for="SearchTypeActive">
<span >Search <u>only</u> active requests</span>
</label>
<input class="ml-3" name="SearchType" type="radio"
id="SearchTypeAll" value="All">
<label for="SearchTypeAll">Search all requests</label>
</div>

Accessibility Updates for Checkboxes and Datarows

These changes were also applied in the v5.0.73 default web pages release.

Several updates were made to the web pages to fix accessibility issues:

  • Added header classes for h1-h6 elements to the default aeon.css file that can now be used on any element.
  • Updated header elements on certain datarow templates and on webAlerts.js to instead use div elements with the relevant header class in order to fix an issue caused by missing header values on screenreaders.
  • Fixed an invalid aria-labelledby target on webAlerts.js.
  • Updated and standardized "Research Topics" checkboxes on user pages to fix an issue with missing form labels.
These changes impact a large number of web pages. To implement the changes, please overwrite your default web pages with the updated files or make the changes manually on each page found below.

aeon.css

Change this (default lines 7-14):

/*These are CSS classes for the headers*/
h1,h2,h3,h4,h5,h6  {
font-family: 'Open Sans', sans-serif;
}

h1,h2,h3,h4,h5  {
color:#08415c;
}
 

To this:

/*These are CSS classes for the headers*/
h1,h2,h3,h4,h5,h6,.h1,.h2,.h3,.h4,.h5,.h6 {
font-family: 'Open Sans', sans-serif;
}

h1,h2,h3,h4,h5,.h1,.h2,.h3,.h4,.h5,.h6 {
color:#08415c;
}
Note: If your header elements had been previously overridden in custom.css for colors, these changes should also be applied there.

webAlerts.js

Please overwrite this file with the updated file.

Datarow Templates

DataRow_CreditCardOrder.html & RequestsInReviewDataRow.html/DataRow_ReviewRequest.html

Change this:

<h4 class="card-title ">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field='ItemTitle'></a>
</h4>
<h5 class="card-subtitle   mb2 text-muted">
<#DATAROW field='ItemSubtitle'></h5>
 

To this:

<div class="card-title h4">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field='ItemTitle'></a>
</div>
<div class="card-subtitle h5 mb2 text-muted">
<#DATAROW field='ItemSubtitle'></div>

On these lines:

  • DataRow_CreditCardOrder.html (default lines 7-10)
  • RequestsInReviewDataRow.html/DataRow_ReviewRequest.html (default lines 13-16)

DataRow_DefaultActivity.html

Change this (default lines 6-8):

<h4 class="card-title ">
<a href="aeon.dll?&Action=10&Form=91&Value=
<#DATAROW field='Id'>">
<#DATAROW field='Name'></a>
</h4>
 

To this:

<div class="card-title h4">
<a href="aeon.dll?&Action=10&Form=91&Value=
<#DATAROW field='Id'>">
<#DATAROW field='Name'></a>
</div>

DataRow_DefaultRequest.html

Change this (default lines 6-9):

<h4 class="card-title ">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field='ItemTitle'></a>
</h4>
<h5 class="card-subtitle   text-muted">
<#DATAROW field='ItemSubtitle'></h5>
 

To this:

<div class="card-title h4">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field='ItemTitle'></a>
</div>
<div class="card-subtitle h5 text-muted">
<#DATAROW field='ItemSubtitle'></div>

DataRow_ElectronicDelivery.html

Change this (default lines 6-10):

<h4 class="card-title ">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field="ItemTitle"></a>
<span class="text-muted"><#DATAROW field="ItemDate">
</span>
</h4>
<h5 class="card-subtitle   mb2 text-muted">
<#DATAROW field='ItemSubtitle'></h5>
 

To this:

<div class="card-title h4">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field="ItemTitle"></a>
<span class="text-muted"><#DATAROW field="ItemDate">
</span>
</div>
<div class="card-subtitle h5 mb2 text-muted">
<#DATAROW field='ItemSubtitle'></div>

DataRow_OrderBilling.html & DataRow_OrderEstimate.html

Change this (default lines 10-18):

<h4 class="card-title ">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field="ItemTitle">
</a>
</h4>
<h5 class="card-subtitle   mb2 text-muted">
<#DATAROW field='ItemSubtitle'>
</h5>
 

To this:

<div class="card-title h4">
<a href="aeon.dll?&Action=10&Form=63&Value=
<#DATAROW field='TransactionNumber'>">
<#DATAROW field="ItemTitle">
</a>
</div>
<div class="card-subtitle h5 mb2 text-muted">
<#DATAROW field='ItemSubtitle'>
</div>

User Pages

ChangeUserInformation.html & NewAuthRegistration.html

Change this:

<div class="form-check  ">
<label for="form-checkbox ResearchTopicsSharing">
<span class="<#ERROR name='ERRORResearchTopicsSharing'>">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
</span>
</label>
</div>
 

To this:

<div class="form-check ml-3">
<label class="form-check-label <#ERROR name='ERRORResearchTopicsSharing'>"
for="ResearchTopicsSharing">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
 
</label>
</div>

On these lines:

  • ChangeUserInformation.html (default lines 244-250)
  • NewAuthRegistration.html (default lines 272-278)

ExpiredUsers.html

Change this (default lines 248-255):

<div class="form-check ml-3">
<span class="<#ERROR name='ERRORResearchTopicsSharing'>">
<label for="ResearchTopicsSharing">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
</span>
</label>
</div>
 

To this:

<div class="form-check ml-3">
<label class="form-check-label <#ERROR name='ERRORResearchTopicsSharing'>"
for="ResearchTopicsSharing">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
 
</label>
</div>

NewUserRegistration.html

Change this (default lines 251-257):

<div class="form-check ml-3">
<label for="form-check-label" form="inlineFormCustomSelect" class="pl-3">
<span class="<#ERROR name='ERRORResearchTopicsSharing'>">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
</span>
</label>
</div>

 

To this:

<div class="form-check ml-3">
<label class="form-check-label <#ERROR name='ERRORResearchTopicsSharing'>"
for="ResearchTopicsSharing">
<input class="form-check-input" type="checkbox"
id="ResearchTopicsSharing" name="ResearchTopicsSharing"
value="Yes" <#CHECKED name='ResearchTopicsSharing'
default='true'>>May we share your research topics with others?
 
</label>
</div>

Questions?

If this article didn’t resolve your issue, please contact Atlas Support for assistance:

Contact Support