Page Comparison

dcb_admin

dcb_beta_LIBRARY

used for testing feedback issues designated for specific libraries to record outcomes, errors and steps related to dcb capabilities being tested

eg, dcb_beta_lindenwooddcb_by_edge_transaction

requires changes to be made to the dcb transaction module, or a third party edge_ module (such as edge_rtac, edge_users or edge_patrons)

dcb_by_locate

requires changes to be made within EBSCO’s Locate product

dcb_capability_FUNCTIONALITY

application capability or workflow scoped for functional and/or user testing

dcb_catalog_IMPLEMENTATION

dcb_config

dcb_data

dcb_diagnostics

functionality to enhance diagnostic tools or data for troubleshooting request transaction issues

dcb_documentation

dcb_feedback

indicates an issue that has been raised as a direct result of user feedback, typically outside of formal Testing Feedback situations

dcb_folio

dcb_for_locate

changes made to support integration with EBSCO’s Locate product

dcb_harvest

dcb_health

monitoring

dcb_index

dcb_ingest

dcb_i18n

internationalisation and localisation framework and configuration

• use dcb_localisation for changes to translation files

dcb_IMPLEMENTATION_PHASE

work relating to particular implementations and targeted for specific phases.

• implementation = consortium project

• phase = project delivery stage

  • planning, discovery, beta, ops, post-launch

eg, dcb_mobius_beta, dcb_mobius_ops, dcb_mobius_post-launch

dcb_legacy_feature

dcb_localisation

adds new or changes existing translations, including introduction of new or removal of existing supported languages

• use dcb_i18n for work relating to the internationalisation framework

dcb_maintenance

dcb_normalisation

dcb_onboarding

dcb_project

dcb_qol

dcb_release_ACTION

See Release Labels

• dcb_release_reindex

• dcb_release_ingest

dcb_requirements

dcb_support

Issue that has been raised through a customer support channel

dcb_triage

Issue that requires verification and investigation before it is correctly assigned

dcb_ui_CONTEXT

user interface within DCB applications

• dcb_ui_content: text, messages and other microcontent; likely to also include dcb_localisation work

• dcb_ui_presentation: design, layout and styling

• dcb_ui_interaction: admin workflows, component functionality, performance and other interactive behaviour

• dcb_ui_accessibility: accessibility enabling work and exceptions

dcb_validation

Issue includes data validation rules, criteria or workflows

On front-end, may also be accompanied by dcb_ui_interaction

dcb_workflow

request and circulation workflow, as handled within the WorkflowService and client adaptors

dcb_beta_LIBRARY

used for testing feedback issues designated for specific libraries to record outcomes, errors and steps related to dcb capabilities being tested

eg, dcb_beta_lindenwood

dcb_capability_FUNCTIONALITY

application capability or workflow scoped for functional and/or user testing

• dcb_capability_union-catalog-clustering

• dcb_capability_union-catalog-suppression

• dcb_capability_locate-detailed-display

• dcb_capability_locate-facets

• dcb_capability_locate-item-requesting

• dcb_capability_locate-navigation

• dcb_capability_locate-simple-search

• dcb_capability_sierra-circulation