Difference between revisions of "Roadmap 22"

(Special features)
(Special features)
Line 45: Line 45:
 
* {{TAGDONE}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules
 
* {{TAGDONE}} Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules
 
* {{TAGDONE}} Support for partial publications (filtering) [https://sourceforge.net/p/artdecor/tickets/189/ SF#189]
 
* {{TAGDONE}} Support for partial publications (filtering) [https://sourceforge.net/p/artdecor/tickets/189/ SF#189]
 +
 +
==External Services Support==
 +
* {{ProgressBar |90}} ADAWIB allows processing artefacts of very large governance groups
 +
* {{TAGDONE}} ADAWIB allows to export to Mediawiki environments
 +
* {{ProgressBar |50}} ADAWIB allows to export to Confluence environments
 +
* {{ProgressBar |10}} ADAWIB allows to export to WordPress environments
  
 
==Role Based Access to DECOR==
 
==Role Based Access to DECOR==

Revision as of 15:40, 2 March 2020

ART-DECOR Release 2.2 (spring 2020)

Note that some features will be postponed after prioritizing.

Datasets/Concepts

  • Coverage
    80% done
    Support for creating new dataset in ART (scratch/existing), backend done, better UI support to follow SF#152
  • To Do
      
    Support binding a concept/valueDomain to an identification system (scratch/existing) SF#127
  • To Do
      
    Exceptions for all value domains

Templates/Rules

  • Coverage
    80% done
    Support for FHIR resources and profiles SF#184
  • Coverage
    80% done
    Add support for FHIR profiles to act as like other artefacts regarding Building Block Repositories
  • Coverage
    10% done
    Add diagnostics to schematron engine to support assert/report types/categories of errors/warnings SF#284

Value Set

Nothing new planned for this release

Code system support

  • Coverage
    40% done
    Solution for code system authoring, release management SF#177

Building Block Repositories (BBR)

Done
  

Add better statistics function

Scenarios

  • To Do
      
    Implement creating and maintaining Transaction “Defaults” (typical scenarios) SF#8 SF#12 SF#119 SF#17
  • Coverage
    10% done
    Support restricting valuesets/conceptList in a scenario SF#107

Testing

  • Coverage
    90% done
    Live Runtime Compile LRC Validation
  • Coverage
    60% done
    Instance Fragment Validation IVF
  • Coverage
    70% done
    Refactoring the XIS package SF#161 SF#139 SF#80; move to more general approach, support multiple languages
  • Coverage
    70% done
    Support new validation service. Is code X in valueset Y SF#132

Special features

  • Coverage
    90% done
    Difference analysis of DECOR artefacts (per project, on demand)
  • Coverage
    80% done
    Support for v2.xml SF#185 SF#174
  • To Do
      
    Support for HL7 V3 data types R2 SF#140
  • To Do
      
    Implement user settings that remember UI status SF#104
  • To Do
      
    Update/change rich text editor feature set SF#188 SF#50
  • To Do
      
    Refactor OID Viewer SF#193
  • To Do
      
    Refactor OID Manager SF#194
  • To Do
      
    Refactor OID Requests SF#195
  • To Do
      
    Add a formal approval mechanism for transactions, and possibly dataset subtrees SF#201
  • To Do
      
    Add support for subscription on publication sites (ADRAM served)SF#302
  • To Do
      
    Logger for changes in datasets, value sets, templates, with connection to ADANS for change notifications
  • Done
      
    Introduce history storage of DECOR artefacts (template, value set, scenarios/transactions), re-write history mechanism for dataset concepts later to follow the same rules
  • Done
      
    Support for partial publications (filtering) SF#189

External Services Support

  • Coverage
    90% done
    ADAWIB allows processing artefacts of very large governance groups
  • Done
      
    ADAWIB allows to export to Mediawiki environments
  • Coverage
    50% done
    ADAWIB allows to export to Confluence environments
  • Coverage
    10% done
    ADAWIB allows to export to WordPress environments

Role Based Access to DECOR

  • Coverage
    60% done
    Implement more fine grained role based access to DECOR. As is currently the case, everyone regardless of role, has read access. You need to be someone with a specific background to gain write access too. You need to be appointed specially to also perform certain tasks such as finalizing a dataset/value set/template. This last category of tasks is dubbed authorization. The exact user stories behind each role and maybe a better name then "authorize" is to be determined. This proposal should also include xis (and xis-admin?), governance groups and communities. Proposal:
read/write authorize
decor-admin all all
dataset-editor dataset
dataset-admin dataset dataset
terminology-editor terminology
terminology-admin terminology terminology
scenario-editor scenario
scenario-admin scenario scenario
templates-editor templates
templates-admin templates templates
issues-editor issues issues
Table: Role Based Access setup for DECOR