Aurora Web Service (AWS) Release Notes – 2012 #
Details are displayed in reverse chronological order (latest first)
| Version | Change | Detail |
|---|---|---|
| 2.12.20.33794 | Enh | Adjustments to handle multiple 007 tags correctly in a cataloguing record |
| 2.12.18.25450 | Enh | Further modifications to support Workstations parameter maintenance |
| 2.12.18.25450 | Enh | Slight adjustment applied to suppress a message from the AWS Log, where the library has not yet moved up to Schema 174. [Loan_SubLimits. LIM_Combo as per reference 2.11.30.30422 below] |
| 2.12.17.0 | Fix | Temporary, permanent and transfer clearance transactions (26,27,28) now all write the item’s format to the CC_Format field in the CirculaitonHistory table |
| 2.12.13.0 | Fix | An error was identified in handling SMS messages, and this is fixed in this version |
| 2.12.11.30634 | Rnh | Changes are applied for managing Reservation queues in a Consortium – e.g. to calculate queues by Council Entituy |
| 2.12.10.31934 | Enh | A new Enterprise parameter called HoldingsTagsToNotDrop is added allowing definition of local holdings subfields e.g. $7 – setting them not to be dropped as part of import processes |
| 2.12.8.29463 | Enh | Modifications to support Workstation maintenance functions in Desktop |
| 2.12.6.31543 | Enh | New logic is added for control of renewals in a Consortium, If a user renews an item owned by one Council on an OPAC or workstation run by another Council within a Consortium, then AWS will apply the loan renewal parameters of the owning library and not those of the library where the transaction occurred. |
| 2.12.5.33209 | Enh | Following on from the previous change, where a reservation is placed which is explicitly NOT within the matched Council elements as described, then this is noted by default as an INTRA-Library Loan Request, and this is marked with I in ReseerveQueue. RSV_Grade for the reservation, and as CirculationHistory. CC_Override, for related transactions. |
| 2.12.5.33209 | Enh | Changes are applied to allow tighter control of reservations within a consortium, to allow restriction of reservations to the user’s own Entity. A new Enterprise parameter called ReserveMustItemEntity is added and where this set to true (1) then an item which is returned must have its ‘item home Council’ match the ‘collect at Council’.If not the reserve won’t be trapped when the item is returned |
| 2.12.1.31322 | Enh | Further additional logic is applied to the handling of sublimits. The limit now has the following enhanced meanings for a limit value:
If an unlimited amount is required for the limit, then this should be set as 9999 |
| 2.11.30.30422 | Enh | New logic is applied to Loan SubLimits – to allow for situations where different Material types have individual limits, but are controlled so that individually they may have variant limits according to user type, e.g. where Material type A has a limit of 8, but associated Material typs B and C each have limits of 4 for all users, but zero for some users. These definitions are now supported through use of a new Loan_LoanSublimits field (LIM_Combo) applied in Schema 174 |
| 2.11.28.29435 | Enh | Changes are now allowed in the following Charge parameters, to allow variation in a Consortium according to entity:
|
| 2.11.27.24156 | Fix | An issue was found in the matching of loaded records with embedded Holdings data. If the second record finds an existing holding that it can reuse and this has a different item format, the load process was updating the item barcode – but not the item format. This is now fixed. |
| 2.11.9.28515 | Enh | The GetItemDataset method is enhanced to ensure that any item which is created with a Home location as zero will still be found. Previously the indication was that such as item was not on file |
| 2.11.6.19837 | Enh | This new version allows an SQL report to run and be auto emailed to you – with the results zipped to reduce the email size |
| 2.11.1.28544 | Enh | AWS modified to allow transfer of individual items from order to bibliographic records where the full order is not received |
| 2.10.25.33668 | Enh | AWS uses updated dll functions to handle Z39.50 search interactions |
| 2.10.24.30212 | Enh | This AWS version contains improved dataset paging code This is applied in most reads as it is used in the AuroraAccess Class. It will be applied as long as there is not an entry [NEW] in the Inst_Enterprise table called ‘BypassSearchPaging’ with a setting of ‘1’.If your installation either does not have the parameter in place or if it is set to the default ‘0’, then the new paging will be automatically used. |
| 2.10.24.30212 | Enh | Now operating under .Net Framework 4.0. Please note the changes required to run this version. You will need to ensure your instance of IIS is reconfigured accordingly. |
| 2.10.22.25436 | Fix | A situation was identified where a user was set with today’s date as the start point and the Aurora host does not recognise the user as debarred. This is believed to have been caused by the one hour time difference between the client and the server.AWS codeis now modified to compensate for this difference |
| 2.10.15.31412 | Fix | An error was found in the AWS method for order receipt – this applied today’ date to a newly added invoice id, overwriting a manually added date – this is now fixed |
| 2.10.10.34403 | Enh | Previously for a search specifying ‘Must have items’, AuroraSearchCatalogue.DLL checked for the presence of items or a value in the BDDS. DDS_URL field to retrieve images or ebooks. This is now amended to check additionally for presence of keywords XIMAGE or XEBOOK (because any work with a URL will put a value into DDS_URL) |
| 2.10.10.34403 | Enh | AuroraSearchCatalogue.DLL now has the ability to restrict work matches to only those that have items ‘on order’ |
| 2.10.10.34403 | Fix | An error was identified causing a situation where an image URL was not being designated as having an XIMAGE keyword. This is now fixed |
| 2.10.9.27930 | Enh | A change is made to Cataloguing error logging for 008 fault to allow both 008 and equivalent 006 values to be returned in the error message |
| 2.10.8.29443 | Enh | A new field UserEntityID is added to the method GetUserDataset This is for use in consortium operations where they may be a charge for supply of reservations from one Entity to another |
| 2.10.8.29443 | Enh | AWS now utilises a new section in auWksAurora.ini to set favourite Z39.50 targets. This is used in the new Desktop search function of this date or later |
| 2.10.8.29443 | Enh | AWS now includes an updated Z39.50 search capability |
| 2.10.3.33421 | Fix | A small error in AWS was identified where and AWS fails to recognise ILL works as on file where the status of the work is ‘Inter-Library Loan’. When ILL comes to reserve this work for the user, a ‘missing work’ message was then presented. This is now fixed. |
| 2.9.29.22468 | Fix | The AWS method BuildMarc no longer puts the current chronological year into the 008 date of publication entry for Suggestions. All Suggestions which were loaded into the database were placing the current year into this field. Now 008/07-10 is given 4 spaces unless the data of publication is provided (and is 4 digits) in which case this value is used. |
| 2.9.20.30187 | Enh | AWS is updated to accept a dataset as equivalent to the XML file created by Aurora Task – and place this task file into a folder monitored by Aurora Watcher on the server. This allows an authorised operator anywhere to submit a task to be run; a new screen in Aurora Desktop 2.9.20 or later allows this AWS method to be accessed. |
| 2.9.10.25366 | Fix | It was discovered that the Overdue Renewal transaction was in fact being written to the Transaction History as Overdue Return instead. This is now fixed |
| 2.9.6.29834 | Enh | Item sorting (within a work) options are extended:
|
| 2.9.4.28554 | Enh | The new AWS method Z3950_EmailMarcRecord adds a new Enterprise parameter EmailSentFromZ3950 – to define the email address to be used for sending results of the Z39.50 search; and allows the parameter to be maintained. |
| 2.9.4.28554 | Enh | A new AWS method Z3950_EmailMarcRecord is added. Using this method, Aurora Desktop can invoke a Z39.50 search via the AIT AWS subscription service – allowing sites to close their Port 210 firewall hole and not do their own Z39.50 searching and use the AIT service instead. |
| 2.8.31.29854 | Enh | Enhancements applied for eBook cataloguing, in conjunction with Aurora Backroom 2.8.31 or later:
|
| 2.8.28.30565 | Fix | Corrections to Item Format parameter maintenance – to ensure IM_IgnoreIfOnLoan field is not left NULL and to save IM_IgnoreInIT correctly |
| 2.8.27.25647 | Enh | AWS now allows control of the new Item Format parameter IM_eBook – but please note that this requires update to Schema version 173 |
| 2.8.27.25647 | Enh | This version of AWS adds a new Enterprise parameter ‘ReserveMustItemEntity’, which (if set) checks all items for a selected work to ensure there is one that has a location within the user’s Entity/Council |
| 2.8.24.20443 | Enh | An enhancement is applied to the AWS method GetUserLinks, where the implementation uses Entities for Councils (e.g. QPIL) so that in addition to returning the existing count of items on loan, it now returns extra tables, to identify location (entity) of loan and details of overdue items. In Desktop this it means you can see immediately what item is overdue without having to jump to the separate User Links / Items on Loan display |
| 2.8.23.24654 | Enh | Notices functions now extended to handle Reservation Notices |
| 2.8.23.24654 | Fix | It was noticed that spacing of availability messages in OPAC was not consistent – this is now addressed |
| 2.8.22.29854 | Enh | AWS extended to support ILL operations in Aurora Desktop |
| 2.8.20.26343 | Enh | The method GetParamDataset is extended to allow an SQL query to be invoked and have the results saved to an XML file or to a CSV file (this is a bit slower). This is presented in changes to Aurora Desktop Reports /SQL Query of this date or later |
| 2.8.16.20432 | Enh | A revision is applied to the logic applied where the Enterprise parameter ReserveNoChargeOnShelf is set ON. This has a secondary check to determine if the item had been returned within the past 24 hours, and if so, to allow the charge to be applied. This check is now removed. |
| 2.8.14.33163 | Fix | AWS is updated to ensure that a loan’s due date gets the actual loan time on the due date from the loan parameters. This was separately applied by program logic, and an intermittent fault could mean that the due time was set at 00.00 on the due date – meaning that items returned on that day could then apparently be subject to a fine. This is now fixed |
| 2.8.14.33163 | Enh | AWS is updated to prevent a duplicate email or post Overdue Item Notice being created for the same item as an SMS overdue notice (via an amended GeneralMaintDataset method); therefore, SMS will not be an enlivened option if this version AWS or later is not loaded. |
| 2.7.27.31579 | Enh | Permanent Transfer actions now obey the new Enterprise parameter ‘PermTransitTransfers’. This parameter defines whether an item is automatically put into transit following permanent transfer of the item to another location (rather than performing the transfer action, and then returning the item to invoke transit). |
| 2.7.27.31579 | Enh | AWS modified so that saving a new user alsp sets the date of last activity to today’s date. Previously this was left unset, which could result in users being purged if they had no transactions recorded |
| 2.7.24.29324 | Enh | The modification to apostrophe handling applied in 1.7.6.23144 resulted in the affected strings being repeated in the Search Summary display, at the end of the bibliographic details. These repeated strings are now suppressed |
| 2.7.19.27446 | Enh | AWS now supports a new Method (SetDaisyFlag)This provides options driven within an application to switch this flag on or off. There is no other non-SQL way than through the batch DAISY flag update in Allocation on Demand, as it is tied to the requirement for a corresponding DAISY book in a folder.VNILS want to be able to temporarily suspend some works from being allocated; this method allows the flag to be set in the Cataloguer screen. A history record of the update is written. |
| 2.7.17.27102 | Enh | AWS now capable of sending an EDI order |
| 2.7.14.27964 | Enh | The UserSigninValidity method is modified to include operator validation |
| 2.7.13.25765 | Enh | Where the Inst_Enterprise table includes the new email control fields applied in Backroom ver 2.7.13 or later, these are now used by AWS, i.e. EmailSSL; EmailUseAuthentication; EmailAccountName; EmailAccountPassword; EmailAccountPort |
| 2.7.5.25443 | Enh | AWS revised to support the revised Desktop Notices function – this version or later is required for Notices operation |
| 2.7.4.26172 | Fix | A fault was identified where users joining the library via OPAC could be given a user type of zero. This is now rectified. |
| 2.7.3.28665 | Enh | AWS is extended to allow
|
| 2.6.26.32445 | Enh | AWS now supports a new Method (UserPrivileges)This provides an enhanced method of authentication to allow a library to be able to specify who they will allow to authenticate and have access to eBooks e.g. block users such as under review etc…If one of the following cases is true the user will not authenticate:
Unrestricted = 0
InvalidAccessPoint = 1
NoDatabaseConnection = 2
InvalidOperator = 4
LoginInvalid = 8
UserSigninInvalid = 16
UserNotFound = 32
Debarred = 64
Expired = 128
AbnormalStatus_Delete = 256
AbnormalStatus_Archive = 512
AbnormalStatus_Review = 1024
AbnormalStatus_Private = 2048
AbnormalStatus_DebarredByCharges = 4096
AbnormalStatus_DebarredByFines = 8192
AbnormalStatus_Deceased = 16384
AbnormalStatus_Unsubscribed = 32768
AbnormalStatus_Unknown = 65536
MoreThanOneUser = 131072
Libraries can bypass any of the situations above in order to allow that condition to be authenticated regardless |
| 2.6.26.32445 | Fix | Modifications made to authority record maintenance to correct a Heading by ensuring it has the Authority ID in the record and that the Bibliographic link count is updated |
| 2.6.21.29743 | Enh | Quick Holdings enabled for the addition of multiple holdings at one time |
| 2.6.4.27653 | Enh | Consistency checks improved while removing a subfield in cataloguing, to ensure that at least some data remains, and not just leave empty tag content |
| 2.6.4.27653 | Enh | AWS now supports a new Method (GeneralMaintDataset) This allows the content of a specific Marc tag to be updated (not added or deleted at this stage). Headings and Holdings cannot be modified this way, as they have associated related tables and need extra procedures in place to maintain them. |
| 2.5.31.26436 | Enh | AWS now extended to support new Inst_System and Inst_enterprise fields for external fund ids. |
| 2.5.12.30452 | Enh | AWS now supports a new Method (WebLinkTransaction). If a user (not operator) chooses to follow an OPAC link, e.g. to view an image (not Syndetics but 856 tag links to images, PDFs, sound files, etc.) – the Aurora application (OPAC or VGallery) will now invoke a new AWS Call to record this event for statistical purposes. This will give the library some idea of how regularly their ebooks, etc. links are being used. |
| 2.5.4.27548 | Enh | AWS now allows for the update and application of ILL status to records in ILL/Suggestions |
| 2.5.3.23445 | Enh | AWS modified to support the new UserCharges field (UCHG_TaxInvoiceID) – it also adds the Tax Invoice id into the Override field in the CirculationHistory table |
| 2.4.18.32395 | Enh | Updates are applied to AWS, so that the GetParamDataset method recognises when a language other than English is used; it then performs an extra step to try to look up the caption. This is necessary as datasets are pulled down and stored on the local PC in XML files and it is essential to ensure that these contain the correct language captions. |
| 2.4.13.29522 | Enh | Licence and workstation details are now shown on the Local Settings / Connections tab. If the operator now clicks the AWS URL displayed, this will now invoke the default Browser (from the registry) and show the AWS page. |
| 2.4.11.28432 | Enh | Modications to save the new Inst_System. SYextra field. This will require a Schema update to v172 (not yet released) |
| 2.4.11.28432 | Enh | Changes are made so that a replacement cost addition or change made to a Holdings record in the Cataloguer screen will now be passed to and saved into the item record.If you assign a $r replacement cost of zero and save the record, this will zero any existing item replacement cost; but if the Holding replacement cost field is cleared and no value is given, this will drop the 852 $r field – but the change will not zero any existing item record replacement cost,as a replacement cost can be added in Item Details without requiring a 852$r value |
| 2.4.3.30235 | Enh | Now permits save of new or modified Material Type parameters. This will require a Schema v170 |
| 2.4.2.29075 | Enh | A modification is applied to loan parameter controls, allowing for the use of the wildcard zero to be represented in Location or User Type or Material Type – separately or in combination, allowing for the rationalisation of parameters, and reduction in need for duplication |
| 2.3.28.23787 | Fix | AWS did not allow Cataloguing editing to change and save an item barcode within the MARC display – this is now fixed |
| 2.3.26.24567 | Enh | AWS extended to allow System parameters to be updated |
| 2.3.14.32384 | Enh | Additional checks applied for operator id update when in an Active Directory environment |
| 2.3.1.28374 | Enh | A new Enterprise parameter is supported (this is applied in Backroom of this date and later) – the parameter is ‘HoldingSubLocnBump’. The default setting for this parameter is False (0), and in the default setting there will be no change to functions. If the parameter is set to True (1) then this has important significance in the loading of Supplier bibliographic records with embedded holdings tags. The scenario envisaged here is specifically where the supplier is providing linked sets of records – brief initial records, and fully completed updated records. If the default setting is in use, then the holdings (852) subfields $a and $b must match to allow merge of the fields; if there is no match on these elements then the update will cause additional 852 tags, and therefore incorrect holdings, to be created. With this new parameter set to True, the $b (sub-location) in an existing 852 tag will be overwritten, if it has no existing Item barcode ($p) and the incoming supplier Holding does.This should not be set without preliminary testing. |
| 2.2.27.27120 | Fix | Recent developments introduced a bug which did not delete reservations or requests if the item being loaned to the reserving user (after it was trapped) had a part number greater than 1. The user status summary would then continue to indicate that there was a reservation waiting to be collected. The nature of the error, indicating a part number, means that this is primarily a problem with Magazine reservations. This is now fixed. |
| 2.2.16.15965 | Enh | AWS now allows support for identification of ‘near match’ in Cataloguing. If a Near Match is identified, this will cause a stop on the save process; the screen will explain and place the matching USRI into the Clipboard. You can then look in Catalogue search screen to see the Marc content and then decide if the current record is a new or changed record; then go back to Cataloguing, go to Options, and select a new radio button to add as new or as a changed record.This requires Backroom/Desktop 2.2.16 or later |
| 2.2.16.15965 | Fix | The saving of the User Subscription day of the week as ‘Any’ was not allowed, and traced to an error in AWS. This is now fixed |
| 2.2.9.27625 | Fix | Fix to reservation ‘expiry’ date to prevent it appearing as expiring ‘on today’s date’ |
| 2.2.7.27443 | Fix | An error was identified in handling spaces embedded in a Z39.50 search for an ISBN. This is now fixed. |
| 2.2.1.32604 | Enh | Changes applied so that Charge information may be limited according to operator language setting |
| 2.2.1.32604 | Enh | A new AWS method UserDebarralClearance is provided. Its purpose is to allow a one click acceptance of Membership terms and conditions where the user has been auto-debarred by the Aurora Task update, as a result of their age changing to Adult.The method only applies where the user has the debarral code 93 (auto applied by the Task update). In this case, it will remove the debarral from the user and reset Membership acceptance as of today. It also writes a UserHistory record of this transaction.The Review status on the user (also set by the Task Update) will remain. |
| 2.1.25.29545 | Enh | An additional options is added to the ReturnAnItem method to allow an item to bypass a reservation trap. This is required by VNILS for handling of Download on Demand items, to avoid Instant Turnaround. [for testing, add 8192 to te value currently being passed as a RunTimeParameter integer value] |
| 2.1.18.31351 | Fix | A syntax error was identified; this version is released as an Important Patch that should replace previous versions |
| 2.1.17.30927 | Enh | The handling routine for conversion of CJK records is modified to cater for non-standard exceptions encountered |
| 2.1.17.30927 | Enh | AWS extended to copy an incoming, as in Load, 852$z (public note) to StaticItem. IS_Msg, to act as an item message, e.g. ‘2 discs’
|
| 2.1.16.29123 | Enh | Modifications to saving of DDS_SExx fields in BDDS, to ensure correct application of punctuation |
| 2.1.16.29123 | Enh | AWS modified to allow the Addition, Change and Deletion of Korean data into Inst_System parameters in conjunction with Backroom of this date or later |
| 2.1.12.30721 | Enh | Changes to indexing to ensure all instances of ISBN in a bibliographic record are indexed |
| 2.1.5.21233 | Enh | A new AWS Method SendAnEmailDataset is provided. The difference between this and the existing method SendAnEmail is that using the dataset passed through in the new method it is able to contain extra information not in the SendAnEmail argument list. This new method is employed in Aurora Post as well as replacing the earlier method in applications |
| 2.1.3.17343 | Fix | A change is made to cataloguing validation to ensure that a second date of 9999 is accepted (008/11) |