imls-dmt / imls-dmt/imls-dmt-api
Clone current devel SOLR database to retain as new production database, with clone as the new development database
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 30m
- Merged PRs (30d)
- 4
Description
As we are shifting the development system to production the current contents of the development instance will be retained as the production database. A clone of the current development database will then be used as the supporting database for the development platform. From that point forward the development database will contain non-persistant/non-authoritative data in support of continuing development efforts.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by identifying how the current development and production database instances are provisioned and used, then confirm the required clone and cutover procedure; done means the existing development contents are retained for production and a clone supports development.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100