Library:Resource Pages Application Workflows and policies

From UBC Wiki
Jump to: navigation, search

This page outlines policies related to the Resource Pages Application.

Roles and responsibilities

  • The curation and maintenance of Resource Pages are a collective responsibility.
  • For the most part, librarians and support staff will be responsible for the creation and editing of all subject-specific and trial resource pages.
  • eResources & Access (eR&A) staff will set up “generalized” resource pages (for example Academic Search Complete or Gale NewsVault).
  • eR&A staff will take care of the URL and EZproxy for all resource pages.
  • Only eR&A staff will have enhanced permissions to publish and delete resource pages.

Levels of access

  • Subject librarians & support staff – can create and edit resource pages. To unpublish or delete pages, send a request to eR&A staff using the links in the resource page admin side.
  • eR&A – can create, edit , publish, unpublish (i.e. mask), and delete resource pages.


  • Resource pages exist to aid discovery, authentication and access. Resource pages should comprise a carefully-curated listing of resources; it is not meant to be an all-inclusive portal.
  • Resource pages are assigned "owners" (usually the librarian responsible for the relevant subject area). Since owners of resource pages are responsible for their curation, care should be taken to create only as many resource pages as the owner has time to regularly review and update.
  • Resource pages generally focus on resources subscribed to or acquired by the library.
  • Resource pages are only created for resources that can’t reasonably be discovered elsewhere (for instance, through Summon or the catalogue) or have special authentication / access issues. This policy applies in particular to freely-available resources. Free resources that can simply be found through a Google search (for example, other libraries’ catalogues) generally do not merit resource pages.
  • Resource pages may be created for important “free” resources, but only at the broadest yet still distinct level available for the items (i.e. a resource page for “TreeSearch”, not individual resource pages for U.S. Forest Service Reports, Manuals, etc.).
  • The same principle of featuring a resource page for the broadest level of a distinct collection also applies to subscription or purchased resources. For example, one resource page for “Oxford Scholarship Online” is recommended, rather than separate resource pages for each individual sub-collection (such as the music section).
  • A database on a platform that also hosts other databases (for example, Medline on OvidSP) is considered to be at a level of granularity and distinctness that merits a resource page. For database segments/subsets, or sub-collections, consider instructing users to rely on the native features of the interface rather than creating multiple resource pages. For example, the working group advises against creating a separate information page for the Medline In-Process & Other Non-Indexed Citations segment. This is not a hard and fast rule, as there may be good reasons for supplying multiple resource pages. However, keep in mind the first principle of carefully curating a collection of resource pages. The more pages there are, the more onerous to update information in a timely manner.
  • In general, only ONE access URL per resource page is permitted. There may be a very small number of exceptions made by the eResources unit for unusual cases; however, database segments/subsets are not such an exception (i.e. if a librarian deems separate pages for subsets or sub-collections essential, he or she will be responsible for creating and maintaining these separate pages.)

Go back to Resource Pages Application Manual homepage