Note, configuration and theme changes that exist in the xmlui or jspui module will need to be re-engineered for the DSpace 7 frameworks.
Where feasible, existing DSpace configuration settings should migrate unchanged. This document enumerates the specific files in dspace/config that will need to be migrated for DSpace 7.
Assumptions
- Instances that have not yet upgraded to DSpace 6 will need to upgrade configuration files to be compatible with DSpace 6
- See "Update your DSpace Configurations and/or move them to local.cfg" on the following page: Upgrading DSpace
- The traditional DSpace workflow will be deprecated and replaced with XML Workflow.
- The existing processes to upgrade from traditional workflow to XML Workflow will be executed.
- See
- Custom embargo functionality (pre DSpace 3.0)
- A migration path for custom embargo will be needed.
- See
Obsolete or UI-specific configuration files in dspace/config (will need to change)
- modules
- controlpanel (assumes xmlui)
- elastic-search
- spring
- xmlui.xconf
Anticipated Changes
- modules
- dspace.cfg
- TODO: more details on what will change here
- item-submission
- news-side, news-top, news-xmlui
Under Consideration
It is not yet clear if/how the following configuration files might change.
- modules
- input-forms
- re-use as is or provide automatic migration
- workflow-curation
- workflow
What should not change
- controlled vocabularies
- crosswalks
- email templates
- modules
- rdf configs
- altmetrics
- bulkedit
- citation-page
- clamav
- curate
- discovery
- fetchccdata
- google-analytics
- healthcheck
- oai
- publication-lookup
- rdf
- solr-statistics
- solrauthority
- spring.cfg
- submission-curation
- sword-client
- sword-server
- translator
- usage-statitics
- versioning
- registries
- spiders
- spring
- config-definitions
- dc2mods
- default.context
- default.license
- dstat
- dstat.map
- ehcache (from DSpace 6)
- hibernate (from DSpace 6)
- launcher
- local.cfg (from DSpace 6)
- log4j
- sfx