October 2011

RDA Toolkit Release - November 8, 2011

A new release will be pushed to the live site of RDA Toolkit on November 8, 2011. When there is a new release for RDA Toolkit, it is made on the second Tuesday of the month. Releases typically contain updates to content and metadata, enhancements to RDA Toolkit functionality, and fixes to existing bugs. You can subscribe to our RSS news feed to get notification of releases.

RDA-25 Single User Login

Use Case

Current users that are part of an institutional subscription and are not IP authenticated must do a double login. In order to gain full access to RDA Toolkit they must log in using their institutional user name and password and then log in again using their profile name and password. This issue does not apply to Solo-user subscriptions.

RDA-37 Fix TOC for AACR2 22.8

Description

AACR2, the title for 22.8 (in the left hand column) lists itself as "Entry under Given Name, Etc. 11". "11" comes from a footnote number in the text and should not be in the display in the left hand column.

RDA-10 User-Defined Inactivity Timeout

Use Case

Currently the timeout on RDA Toolkit is set at 60 minutes of inactivity. Some institutions with large staffs would like the timeout to be shorter so that concurrent users are freed up sooner, and the institution can share a smaller number of concurrent users. Other institutions would like the timeout to be longer so that users are not timed out of the system and required to log in repeatedly through the day.

RDA-26 Input URL into Annotation of Bookmark

User Case

Users would like the ability to link to local documentation, be it a Workflow, staff wiki, or some other documentation hosted on the Web.

RDA-29 Improve "Email My Password" Function

Use Case

The current "Email My Password" function is only available for users profile name and password. It does not email institution user name and password. The function is only visible after a user is authenticated (via IP or User Name) and is not at all available to solo-users.

RDA-12 Valid Email Address as Profile Login

Use Case

In order to create an "email my password" function (see RDA-29), each profile must be associated with a unique email address. Requiring users to use their email as their login helps to enforce the use of a unique email address for each profile and reduces the likelihood of unintentional duplicate profiles.
Users are often confused by the authentication (user name) and profile logins used by RDA Toolkit. Switching the profile login to an email address will help to differentiate between the two logins.

RDA-27 Edit or Rename Bookmarks

Use Case

The current bookmark tool does not allow for bookmarks to be edited or renamed. The only way to edit or rename a bookmark is to create a new one with a new name, copy over the content, and delete the old one.

RDA-32 Add Section for Locally Shared Workflows and Mappings

Use Case

Currently there are two sections for both Workflows and Mappings. They are sorted by shared Workflows/Mappings and your Workflows/Mappings.

RDA-6 Redesign GUI with icons

Use Case

As RDA Toolkit plans for the introduction of non-English versions, it becomes necessary to use icons rather than words to express navigation choices and functionality. The current page design, with its English text links, is not sustainable in a multilingual environment. The length of the current text links would vary greatly depending on the language, upsetting the page geometry and requiring additional design costs for each version.

RDA-28 Share Bookmarks

Use Case

Bookmarks are used to alert users to local policy decisions and to link to local training aids. Sharing Workflows and Mappings within an institution is a useful way to collaborate with colleagues, and the same would be true for sharing bookmarks. Unlike Workflows and Mappings, sharing bookmarks outside of one’s institution would be less useful and would most likely add unneeded clutter to the display.

RDA-24 Add Metadata to Workflows

Use Case

Workflows and Mappings on RDA Toolkit are powerful tools that are likely to proliferate over time. As the number of these items grows users need the ability to filter, search, and sort user-created content to ensure finding the most useful information.