Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Project Administration

Jira Components

Jira Labels

  • All DCB project labels are prefixed dcb_., followed by a scope and context

    • prefix, scope and context are separated by underscore

    • prefix and scope should be alphanumeric

    • context may have hyphens to separate words

  • Label construction is dcb_SCOPE_specific-context

System Components

Implementation Labels

Deprecated Labels

Label Pattern

Description

Context Examples / Options

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_lindenwood

dcb_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_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

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_health

monitoring

dcb_index

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

  • dcb_release_reindex

dcb_requirements

dcb_support

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_workflow

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

Jira Filters

Project Epics

https://openlibraryfoundation.atlassian.net/issues/?jql=project%20in%20(%22Direct%20Consortial%20Borrowing%22)%20and%20type%20in%20(Epic)%20and%20resolution%20in%20(EMPTY,%20Done)%20ORDER%20BY%20summary

  • No labels