Versions Compared

Old Version 87

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 88

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reorganize tasks in priority listing to align with what we are currently working on in DSpace 7

...

Single built-in Statistical Engine (SOLR Statistics)  Elasticsearch Usage Statistics were deprecated in 6.0 and will be removed in 7.0Non-functional: Module Framework and RegistrySimplify Community and Collection HierarchyLower the effort to deposit content (via integrations)
Advanced Tables - Table Plus
autoNumbertrue
enableSortingfalse

Candidate Features for DSpace 7.0 - Priority 1

The DSpace 7.0 release is under development and the latest status can be found at DSpace Release 7.0 Status. The below candidate features are ordered in terms of importance to the 7.0 release. As such, the goal is to achieve each feature in the order that they appear (and not all features are guaranteed to be completed in time for 7.0). However, if you or your institution would like to drive or lead the development of a specific feature, you are welcome to volunteer your time towards any of the candidate features listed, no matter where that feature ranks in the listing. For larger features/contributions, we recommend first forming a Working Group (anyone can chair or form a Working Group) to allow other institutions to contribute to your initiative.

Working Group

and

DSpace 7 UI Outreach Group

Configurations in Admin User Interface
Priority 1 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse CasesWork in Progress?

Anchor
Single User Interface
Single User Interface
Single User Interface. 
(Work has begun at in DSpace 7 Working Group)

DSpace currently maintains two user interfaces in parallel (JSPUI and XMLUI). We want to "converge" on a To replace these two user interfaces, we are building a new, single, out-of-the-box user interface for DSpaceon Angular.io.

Goal 2: Lean and flexiblexHigh

For reference:

Also see: DSpace 7

Anchor
Configurations in Admin User InterfaceConfigurations in Admin User InterfaceDSpace should support the modification of most configurations/settings from the Administrative User Interface, instead of requiring such configurations be tweaked from command line.
  • Dependent on / related to "Single User Interface"
Goal 5: Low cost, "just works"xHigh
Expand
titleConfiguration Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-configuration" and space = "DSPACE"
labelsuc-configuration

 
Anchor
Single built-in Statistical EngineSingle built-in Statistical EngineDSpace currently has three built-in statistical engines, one based on Apache Solr (default), another based on Elasticsearch (optional), and a third Legacy statistics (which parses logs). DSpace should only provide one out-of-the-box, built-in statistical engine (Solr Statistics), and all others should be removed (and as necessary, their features merged into one).
Goal 2: Lean and flexiblexMedium  
Anchor
Module Framework and RegistryModule Framework and Registry

DSpace needs a clear definition of what constitutes a "DSpace module", so that third-parties can create, maintain and distribute their own "modules" as add-ons to DSpace, and distribute them via a public "registry".

Goal 3: Can be "extended"xHigh  
Anchor
Simplify Community and Collection HierarchySimplify Community and Collection Hierarchy

DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections.

Goal 2: Lean and flexiblexHigh 
Anchor
Lower the effort to deposit contentLower the effort to deposit content

The DSpace deposit process should integrate more closely with external data sources, in order to automatically populate (or suggest) data on deposit. We should also investigate whether some integrations may allow opportunities for Administrator's to autopopulate DSpace from trusted, external content sources.

Goal 1: Fundamentals of IR

Goal 4: Integration with external services

xMedium 

Short Term - Priority 2

As "priority 2" features, these features are not guaranteed for the next DSpace release, but are still seen as a priority in an upcoming release. Nonetheless, we'd encourage community members to volunteer to help achieve any of these features. If there is community interest in moving one or more of these features forward, that feature may be moved up to "priority 1" for the next release.  These features are ordered in terms of importance, but are all considered to be lower importance than the "priority 1" features listed above.

UI Project Plain Language Summary

(tick)

Anchor
Standards-based REST API
Standards-based REST API
Standards-based REST API
(Work has begun in DSpace 7 Working Group)

DSpace's current REST API, while functional, is limited in features and does not follow current best practices for RESTful APIs.

To support the new, single user interface (on Angular.io), we are building / designing a new REST API that follows modern best practices such as: HATEOAS (Hypertext As The Engine Of Application State), ALPS (Application Level Profile Semantics), and using the HAL (Hypertext Application Language) response format.

The new REST API is being built using Spring technologies (Boot, MVC, and HATEOAS).

Goal 3: Can be "extended"

and

Goal 4: Integration with external services

xHigh

New REST Contract (work in progress):

(tick)

Anchor
Single Approval Workflow system
Single Approval Workflow system
Single Approval Workflow system.
(Work has begun in DSpace 7 Working Group)

DSpace currently has two approval workflow systems:

  1. Basic/Traditional Approval Workflows. These are enabled by default, and provide up to three approval steps: "Approve/Reject", "Approve/Reject/Edit", or "Edit". These are described in more detail in the Functional Overview#WorkflowSteps
  2. Configurable Workflow (XMLUI only, and requires migrating all Basic/Traditional workflows)

We should consolidate on a single Approval Workflow system, likely the Configurable Workflow, with sane defaults. See this ticket for more details:

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyDS-3041

Goal 1: Fundamentals of IRxMedium
(tick)

Anchor
Single built-in Statistical Engine
Single built-in Statistical Engine
Single built-in Statistical Engine (SOLR Statistics) 


Elasticsearch Usage Statistics were deprecated in 6.0 and will be removed in 7.0

DSpace currently has three built-in statistical engines, one based on Apache Solr (default), another based on Elasticsearch (optional), and a third Legacy statistics (which parses logs). DSpace should only provide one out-of-the-box, built-in statistical engine (Solr Statistics), and all others should be removed (and as necessary, their features merged into one).
Goal 2: Lean and flexiblexMedium  

Anchor
Configurations in Admin User Interface
Configurations in Admin User Interface
Configurations in Admin User Interface

DSpace should support the modification of most configurations/settings from the Administrative User Interface, instead of requiring such configurations be tweaked from command line.
  • Dependent on / related to "Single User Interface"
Goal 5: Low cost, "just works"xHigh


Expand
titleConfiguration Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-configuration" and space = "DSPACE"
labelsuc-configuration



Anchor
Module Framework and Registry
Module Framework and Registry
Non-functional: Module Framework and Registry

DSpace needs a clear definition of what constitutes a "DSpace module", so that third-parties can create, maintain and distribute their own "modules" as add-ons to DSpace, and distribute them via a public "registry".

Goal 3: Can be "extended"xHigh  

Anchor
Lower the effort to deposit content
Lower the effort to deposit content
Lower the effort to deposit content (via integrations)

The DSpace deposit process should integrate more closely with external data sources, in order to automatically populate (or suggest) data on deposit. We should also investigate whether some integrations may allow opportunities for Administrator's to autopopulate DSpace from trusted, external content sources.

Goal 1: Fundamentals of IR

Goal 4: Integration with external services

xMedium 

Short Term - Priority 2

As "priority 2" features, these features are not guaranteed for the next DSpace release, but are still seen as a priority in an upcoming release. Nonetheless, we'd encourage community members to volunteer to help achieve any of these features. If there is community interest in moving one or more of these features forward, that feature may be moved up to "priority 1" for the next release.  These features are ordered in terms of importance, but are all considered to be lower importance than the "priority 1" features listed above.

Hierarchical Metadata SupportRelationships between ObjectsEnhance Basic Statistical ReportingDSpace's existing Statistical Reporting user interfaces are rudimentary and do not provide enough useful views/reports/exports of the underlying captured data. These should be enhanced based on modern use cases/needs.
  • Primary use case description: Basic Statistics (and all child pages)
  • This would likely be depending on the "Single User Interface" project for much of the enhancements, as many of these reports are UI related.
Enhance Basic PreservationEasy and Intuitive Deposit InterfaceDSpace's deposit interface could use enhancement for a better overall user experience with regards to usability and accessibility.
  • Dependent on / related to "Single User Interface"
  • Primary use case description: Easy and Intuitive Deposit Interface
  • May need further definition around what sorts of changes will make deposit easier?
Priority 2 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse CasesWork in Progress
Anchor
Hierarchical Metadata Support
Hierarchical Metadata Support
Hierarchical Metadata Support
DSpace should support hierarchical metadata formats (e.g. MODS)Goal
Priority 2 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse CasesWork in Progress
Anchor
Hierarchical Metadata SupportHierarchical Metadata SupportDSpace should support hierarchical metadata formats (e.g. MODS)Goal 1: Fundamentals of IRxHigh 
Anchor
Relationships between ObjectsRelationships between Objects

DSpace should support defining relationships between objects (especially at the Item and Bitstream level). Some object relationships may be definable via metadata, but should be respected by the DSpace UI.  But, in other situations, it may also necessitate the creation of new types of Objects (e.g. Author objects as Authors of an Item rather than simply textual metadata)

Goal 1: Fundamentals of IRxHigh 
Anchor
Relationships between Objects
Relationships between Objects
Relationships between Objects

DSpace should support defining relationships between objects (especially at the Item and Bitstream level). Some object relationships may be definable via metadata, but should be respected by the DSpace UI.  But, in other situations, it may also necessitate the creation of new types of Objects (e.g. Author objects as Authors of an Item rather than simply textual metadata)

 
Anchor
Enhance Basic Statistical ReportingEnhance Basic Statistical ReportingGoal 1: Fundamentals of IRxMediumHigh 
 

Anchor

Enhance Basic PreservationEnhance Basic PreservationDSpace's existing basic preservation functions (format identification, checksum verification, etc) could use enhancement based on modern tools and services.
  • See linked use cases for more details of possible enhancements to existing basic preservation functionality
Goal 1: Fundamentals of IRxMedium

Simplify Community and Collection Hierarchy
Simplify Community and Collection Hierarchy
Simplify Community and Collection Hierarchy

DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections.

Goal 2: Lean and flexiblexHigh

Anchor
Enhance Basic Statistical Reporting
Enhance Basic Statistical Reporting
Enhance Basic Statistical Reporting

DSpace's existing Statistical Reporting user interfaces are rudimentary and do not provide enough useful views/reports/exports of the underlying captured data. These should be enhanced based on modern use cases/needs.
  • Primary use case description: Basic Statistics (and all child pages)
  • This would likely be depending on the "Single User Interface" project for much of the enhancements, as many of these reports are UI related.
 
Anchor
Easy and Intuitive Deposit InterfaceEasy and Intuitive Deposit InterfaceGoal 1: Fundamentals of IRxMedium
Expand
titleOther Deposit Use Cases

Content by Label
showLabelsfalse
max20
spacesDSPACE
showSpacefalse
cqllabel = "uc-deposit" and space = "DSPACE"
labelsuc-deposit

 

Longer Term Features / Priorities

While these features are unscheduled at this time, we still encourage volunteers to begin to analyze or tackle them. If there is interest in moving one or more of these features forward in the nearterm, we can immediately schedule it for an upcoming release.  These features are unordered, but are all considered priorities for DSpace moving forward.

 

 
Anchor
Enhance Basic Preservation
Enhance Basic Preservation
Enhance Basic Preservation
DSpace's existing basic preservation functions (format identification, checksum verification, etc) could use enhancement based on modern tools and services.
  • See linked use cases for more details of possible enhancements to existing basic preservation functionality
Goal 1: Fundamentals of IRxMedium 
Anchor
Easy and Intuitive Deposit Interface
Easy and Intuitive Deposit Interface
Easy and Intuitive Deposit Interface
DSpace's deposit interface could use enhancement for a better overall user experience with regards to usability and accessibility.
  • Dependent on / related to "Single User Interface"
  • Primary use case description: Easy and Intuitive Deposit Interface
  • May need further definition around what sorts of changes will make deposit easier?

Goal 1: Fundamentals of IR

xMedium


Expand
titleOther Deposit Use Cases

Content by Label
showLabelsfalse
max20
spacesDSPACE
showSpacefalse
cqllabel = "uc-deposit" and space = "DSPACE"
labelsuc-deposit


 



Longer Term Features / Priorities

While these features are unscheduled at this time, we still encourage volunteers to begin to analyze or tackle them. If there is interest in moving one or more of these features forward in the nearterm, we can immediately schedule it for an upcoming release.  These features are unordered, but are all considered priorities for DSpace moving forward.

Non-functional: Easier InstallationNon-functional: Easier Upgrade ProcessWhile DSpace's upgrade process continues to improve, it is still complex with regards to local customizations or theme changes. We should investigate of simplifying the upgrade process, by alleviate the manual process of merging in local changes/tweaks where possible.
  • Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI
  • Could be helped by "Theme management in Admin UI"
  • )
Advanced Usage StatisticsTheme management in Admin UI

While DSpace currently supports some basic theming in the XMLUI interface, management of such themes is performed via command-line configurations and tweaks. We should find a way to make Themes selectable and tweakable via the Admin UI, like other modern web facing systems.

  • Dependent on "Single User Interface"
  • Could be highly beneficial to "Easier Upgrade Process" in that theme management is a huge pain point of the existing upgrade process
  • Ranked lower in 2013-14 Vision Survey
Enhance Versioning
FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse CasesWork in Progress
Anchor
Easier Installation
Easier Installation
Non-functional: Easier Installation
While DSpace's installation process continues to improve, it is still highly manual in nature. We should investigate ways to provide an "easy installer" which could potentially even auto-install and configure prerequisites such as Tomcat, Postgres, etc.
FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse CasesWork in Progress
Anchor
Easier InstallationEasier InstallationWhile DSpace's installation process continues to improve, it is still highly manual in nature. We should investigate ways to provide an "easy installer" which could potentially even auto-install and configure prerequisites such as Tomcat, Postgres, etc.
  • Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI)
Goal 5: Low cost, "just works"x 
  • There was an older Installer Prototype which attempted some of this, but was not successful. It may be worth revisiting that prior work/experience, if just for use cases.
  • Ability to perform an installation from a CD/DVD or offline is also of importance to institutions where network speeds are lower (mentioned at OAI9 in Geneva in 2015)
  • Vision: Installing DSpace could mean simply installing its UI. Once the UI is installed, you would be prompted to optionally install plugin(s) which enable OAI, SWORD, REST, etc.
 
Anchor
Easier Upgrade ProcessEasier Upgrade ProcessGoal 5: Low cost, "just works"x 

 

 
Anchor
  • There was an older Installer Prototype which attempted some of this, but was not successful. It may be worth revisiting that prior work/experience, if just for use cases.
  • Ability to perform an installation from a CD/DVD or offline is also of importance to institutions where network speeds are lower (mentioned at OAI9 in Geneva in 2015)
  • Vision: Installing DSpace could mean simply installing its UI. Once the UI is installed, you would be prompted to optionally install plugin(s) which enable OAI, SWORD, REST, etc.
 
Anchor
Easier Upgrade Process
Easier Upgrade Process
Non-functional: Easier Upgrade Process
While DSpace's upgrade process continues to improve, it is still complex with regards to local customizations or theme changes. We should investigate of simplifying the upgrade process, by alleviate the manual process of merging in local changes/tweaks where possible.
  • Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI
  • Could be helped by "Theme management in Admin UI"
Advanced Usage StatisticsAdvanced Usage StatisticsDSpace currently only provides basic statististical reporting functionality. We should investigate ways to provide enhanced, highly detailed reports for users who need them. Likely, this will be implemented as an optional module available via a module registry.
  • Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
  • Ranked very highly in 2013-14 Vision Survey
Goal 3: Can be "extended" High

 

 
Anchor
Theme management in Admin UITheme management in Admin UIGoal 5: Low cost, "just works"xHigh expand

 

title Theming Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-theming" and space = "DSPACE"
labelsuc-theming

 
Anchor
Enhance VersioningEnhance VersioningDSpace provides an optional, basic Item versioning capability. However, this versioning capability is limited in nature, and not yet fully integrated into all DSpace tools and interfaces. We should find a way to enhance item versioning, and make it more embedded into the system (and API) overall.
  • Ranked lower in 2013-14 Vision Survey
 x 
Anchor
Advanced Usage Statistics
Advanced Usage Statistics
Advanced Usage Statistics
DSpace currently only provides basic statististical reporting functionality. We should investigate ways to provide enhanced, highly detailed reports for users who need them. Likely, this will be implemented as an optional module available via a module registry.
  • Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
  • Ranked very highly in 2013-14 Vision Survey
Goal 3: Can be "extended" High

 

 
Anchor
Theme management in Admin UI
Theme management in Admin UI
Theme management in Admin UI

While DSpace currently supports some basic theming in the XMLUI interface, management of such themes is performed via command-line configurations and tweaks. We should find a way to make Themes selectable and tweakable via the Admin UI, like other modern web facing systems.

  • Dependent on "Single User Interface"
  • Could be highly beneficial to "Easier Upgrade Process" in that theme management is a huge pain point of the existing upgrade process
  • Ranked lower in 2013-14 Vision Survey
Goal 5: Low cost, "just works"xHigh


Expand
titleTheming Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-theming" and space = "DSPACE"
labelsuc-theming


 
Anchor
Enhance Versioning
Enhance Versioning
Enhance Versioning
DSpace provides an optional, basic Item versioning capability. However, this versioning capability is limited in nature, and not yet fully integrated into all DSpace tools and interfaces. We should find a way to enhance item versioning, and make it more embedded into the system (and API) overall.
  • Ranked lower in 2013-14 Vision Survey
 x 


Expand
titleVersioning Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-versioning" and space = "DSPACE"
labelsuc-versioning


 
Anchor
Replace Bundle object with Metadata
Replace Bundle object with Metadata
Replace Bundle object with Metadata (or similar)

In DSpace, a "Bundle" object is just a simple grouping of Files (Bitstreams) (e.g. "THUMBNAIL", "TEXT"). Rather than being its own object, a "bundle" could be more easily replaced with metadata on individual Bitstreams (e.g. dc.type="thumbnail"), or even relationships between Bitstreams (i.e. derivative objects).

  • Primary use case description: Structure - purpose of bundle layer
  • May also be dependent on or related to "Relationships between Objects" project
  • Also see alignment with PCDM, which simply uses metadata on files
Goal 2: Lean and flexiblexMedium 
Anchor
Advanced Preservation
Advanced Preservation
Advanced Preservation
DSpace currently only provides basic preservation tools (format identification, checksum verification, etc) out-of-the-box. We should investigate providing enhanced preservation options (or integrations) for users who need it. Likely, this will be implemented as an optional module available via a module registry.
  • Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
  • Ranked lower in 2013-14 Vision Survey
Goal 3: Can be "extended"  High 
Anchor
Enhance Search / Browse System
Enhance Search / Browse System
Enhance Search / Browse System
While DSpace's search/browse system continues to improve, there are still ways we can improve the user experience of finding items within DSpace.
  • See various unmet use cases labeled "Search/Browse"
  • Dependent on "Single Search / Browse System" feature being completed, to ensure we can more easily implement new Search/Browse use cases
  • Some use cases also dependent on "Single User Interface" being completed
Expand
titleVersioning Use Cases

Content by Label
showLabelsfalse
max30
spacesDSPACE
showSpacefalse
cqllabel = "uc-versioning" and space = "DSPACE"
labelsuc-versioning

  AnchorReplace Bundle object with MetadataReplace Bundle object with MetadataReplace Bundle object with Metadata (or similar)

In DSpace, a "Bundle" object is just a simple grouping of Files (Bitstreams) (e.g. "THUMBNAIL", "TEXT"). Rather than being its own object, a "bundle" could be more easily replaced with metadata on individual Bitstreams (e.g. dc.type="thumbnail"), or even relationships between Bitstreams (i.e. derivative objects).

  • Primary use case description: Structure - purpose of bundle layer
  • May also be dependent on or related to "Relationships between Objects" project
  • Also see alignment with PCDM, which simply uses metadata on files
Goal 2: Lean and flexiblexMedium  AnchorAdvanced PreservationAdvanced PreservationAdvanced PreservationDSpace currently only provides basic preservation tools (format identification, checksum verification, etc) out-of-the-box. We should investigate providing enhanced preservation options (or integrations) for users who need it. Likely, this will be implemented as an optional module available via a module registry.
  • Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
  • Ranked lower in 2013-14 Vision Survey
Goal 3: Can be "extended"  High  AnchorEnhance Search / Browse SystemEnhance Search / Browse SystemEnhance Search / Browse SystemWhile DSpace's search/browse system continues to improve, there are still ways we can improve the user experience of finding items within DSpace.
  • See various unmet use cases labeled "Search/Browse"
  • Dependent on "Single Search / Browse System" feature being completed, to ensure we can more easily implement new Search/Browse use cases
  • Some use cases also dependent on "Single User Interface" being completed
Goal 1: Fundamentals of IRx 
Expand
titleSearch / Browse Use Cases

Content by Label
showLabelsfalse
max20
spacesDSPACE
showSpacefalse
cqllabel = "uc-browse-search" and space = "DSPACE"
labelsuc-browse-search

  AnchorEnhance Access ControlEnhance Access ControlEnhance Access ControlDSpace's access control system (which manages authentication and authorization) is a custom solution that is now nearly as old as the software platform itself. While it functions well enough as-is, replacing it with a comparable third-party, open source AuthN/AuthZ system would simplify our codebase and ongoing maintenance.
  • See various unmet use cases regarding "Access Control"
    • Also see
    JiraserverDuraSpace JIRAserverIdc815ca92-fd23-34c2-8fe3-956808caf8c5keyDS-1566
    Goal 1: Fundamentals of IRx 


    Expand
    titleAccess Control Search / Browse Use Cases

    Content by Label
    showLabelsfalse
    max20
    spacesDSPACE
    showSpacefalse
    cqllabel = "uc-access-control" and space = "DSPACE"
    labelsuc-access-control

      AnchorSingle Approval Workflow systemSingle Approval Workflow systemSingle Approval Workflow system

    showLabelsfalse
    max20
    spacesDSPACE
    showSpacefalse
    cqllabel = "uc-browse-search" and space = "DSPACE"
    labelsuc-browse-search


     
    Anchor
    Enhance Access Control
    Enhance Access Control
    Enhance Access Control

    DSpace currently has two approval workflow systems:

    1. Basic/Traditional Approval Workflows. These are enabled by default, and provide up to three approval steps: "Approve/Reject", "Approve/Reject/Edit", or "Edit". These are described in more detail in the Functional Overview#WorkflowSteps
    2. Configurable Workflow (XMLUI only, and requires migrating all Basic/Traditional workflows)
    We should consolidate on a single Approval Workflow system, likely the Configurable Workflow, with sane defaults. See this ticket for more details:
    DSpace's access control system (which manages authentication and authorization) is a custom solution that is now nearly as old as the software platform itself. While it functions well enough as-is, replacing it with a comparable third-party, open source AuthN/AuthZ system would simplify our codebase and ongoing maintenance.

    • Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyDS-
    3041
    • 1566
    Goal 1: Fundamentals of IRx  


    Expand
    titleAccess Control Use Cases

    Content by Label
    showLabelsfalse
    max20
    spacesDSPACE
    showSpacefalse
    cqllabel = "uc-access-control" and space = "DSPACE"
    labelsuc-access-control


     

    Anchor
    Enhance Approval Workflow capabilities
    Enhance Approval Workflow capabilities
    Enhance Approval Workflow capabilities

    While directly related to the "Single Approval Workflow system" feature (above), DSpace's workflow system(s) do not yet meet all community use cases for approval workflows.

    This feature is a placeholder for enhancing the Approval Workflow system based on the Workflow Use Cases (see list in the "Use Cases" column). However, it is likely somewhat dependent on standardizing on a single Workflow system.

     

    Goal 1: Fundamentals of IRx 


    Expand
    titleWorkflow Use Cases

    Content by Label
    showLabelsfalse
    max20
    spacesDSPACE
    showSpacefalse
    cqllabel = "uc-workflow" and space = "DSPACE"
    labelsuc-workflow


     

    ...