1. Deleted transactions. When the patron's library deletes transactions from the current 90-day database, the system will retain a "shell" of the deleted transactions so that other libraries that might have been involved in the transactions can still access them for critical reporting information.
A deleted transaction looks like this, on the reports table in Ask/Reports/General:
All text is deleted from the transaction history and is replaced by "This transaction deleted by the patron's library." All patron information is deleted as well. What is retained is:
- Question ID
- Patron's institution
- All institutions involved with the transaction
- Received timestamp
- Most recent Updated timestamp
- Resolution code, if assigned
- Descriptive code, if assigned
- Session type
- Wait and Session Times
- Referral information
- Survey received flag and survey results
Retained information is viewable only via the Ask/Reports feature. Deleted transactions are not accessible through the question lists.
Users can include deleted transactions or exclude them (by selecting "All (Not Deleted)" in the limit-by-status menu) in their Ask/Reports,. But note that if excluding the deleted transactions, you are also automatically limiting your view to only those transactions that are currently being worked on at your institution.
2. Indexing and searching in the knowledge bases. Indexing within the knowledge bases has been improved to better support non-English languages and conventions. Although the changes are, for the most part, transparent to users, here is a description of what is happening:
French-, Dutch-, German-, Greek-, and Russian-language KB records are now indexed using "analyzers" (or special linguistic algorithms) that are specific to each of those languages. One result is the "stemming" of certain terms to allow for automatic retrieval of records with terms based on but not exactly the same as the search terms. Records with plurals of the search term, for example, might be retrieved when a singular search term is entered.
In addition, diacritics are ignored in both indexing and searching, so records are retrieved even when a diacritic is missing from the search term. This is true for all languages. Thus, for example, bibliothèque and bibliotheque find the same records in any language, and bibliothèque, bibliothèques, bibliotheque, and bibliotheques all find the same records if the user is using the French analyzer.
The service defaults to the analyzer for the language of the interface the librarian or patron is using. If a user wants to specify that their search term is in a language other than the default, they can choose the desired language on the Advanced Search page.
3. More Home Page links for 24/7 Cooperative users. The MyQuestionPoint home page now has links to policy pages and schedules, in addition to queues, to make consulting these features more convenient.
4. Support and Help links in patron accounts. A link to Support has been added above the Help link in patron accounts.
5. SPAM Descriptive Code. A new code has been added to the list of descriptive codes so users can mark certain transactions as SPAM. This code will become useful for future reporting options currently being explored. At this time, such a device will allow for easy counts of spam if not deleted. (Please see information posted on the blog, http://questionpoint.blogs.com, regarding efforts to deal with spam coming into your QuestionPoint accounts.)
1. File types for attachments. Not exactly a fix, here is a promised list of all the file types not supported by the Answer Attachment feature: .ade, .adp, .bas, .bat, .chm, .cmd, .com, .cpl, .crt, .exe, .hlp, .hta, .inf, .ins, .isp, .js, .jse, .lnk, .mdb, .mde, .msc, .msi, .msp, .ms,t .pcd, .pi,f .reg, .scr, .sct, .shs, .shb,. .url, .vb, .vbe, .vbs, .wsc, .wsf, .wsh
2. Automatic assignments. If libraries have implemented the automatic assignment capability for e-mails, you know that librarians assigned by that method were not being reported in some of the Ask/Reports. That has now been corrected, so that those assignments are reported and displayed just like assignments made via the standard method.
3. Unassigned list. Librarians accustomed to proceding into the Ask module from the "Unassigned" questions link on the home page will find a bug fixed that proved disruptive to workflow. Today, when you select "Unassigned" and then a specific question to open, you are returned to the full list of New questions when you click on the "Return to List" link. With the fix you will be returned to the list of Unassigned questions.