...
Page Properties |
---|
Target release | 2.2.3 |
---|
Epic | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 3ed8d091-172c-31ee-8b1a-f688a0e72656 |
---|
key | GE-216 |
---|
|
|
---|
Document status | |
---|
Document owner | Yaw Nti-Addae |
---|
Designer | KevinPalis |
---|
Tech lead | Angel Manica Raquel |
---|
Technical writers | |
---|
QA | Yaw Nti-Addae |
---|
|
Objective
Success metrics
...
Goal
...
Metric
Assumptions
Milestones
...
Requirements
...
Requirement
...
User Story
...
Importance
...
Jira Issue
...
Notes
...
...
...
...
...
...
Timescope extension (module) that will allow system administrators to add/edit/delete crops from GDM
Information needed
Crop name
Database name
Web application name (WAR)
Seed data
Requirements
| Requirement | User Story | Importance | Jira Issue |
---|
1 | Add crop | Create a PostgreSQL database for the given database name with nomenclature for crop database as “gobii_cropname”, e.g. gobii_maize, gobii_wheat, gobii_rice Populate the newly created database with basic liquibase seed data (context: general, seed_general) Load the given seed data for PI contacts (typically provided by the organization/client) Duplicate the WAR file of an existing crop (ex. gobii_dev.war, gobii_wheat.war) as gobii_<cropname>.war Ensure that the new WAR file is expanded by tomcat (usually via the manager’s redeploy/deploy functionality) Add the corresponding entries to the gobii-web.xml file (the entire crop xml block) Create the new crop’s subdirectory in gobii_bundle/crops/* Create the corresponding cron jobs for the new crop Redeploy the new gobii-*.war application
| | |
2 | Edit crop | Rename PostgreSQL database for the given database name to new name Rename the WAR file of an existing crop (ex. gobii_dev.war, gobii_wheat.war) as gobii_<newcropname>.war Ensure that the new WAR file is expanded by tomcat (usually via the manager’s redeploy/deploy functionality) Edit the corresponding entries to the gobii-web.xml file (the entire crop xml block) Rename the crop’s subdirectory in gobii_bundle/crops/* Rename the corresponding cron jobs for the new crop Redeploy the new gobii-*.war application
| | |
3 | Delete crop | Backup GDM (including files and database) Drop PostgreSQL database for the given database name Edit liquibase to reflect changes Stop web service for crop in Tomcat Remove crop service from Tomcat Edit the corresponding entries to the gobii-web.xml file (the entire crop xml block) Delete crop’s subdirectory in gobii_bundle/crops/* Remove the corresponding cron jobs for crop
| | |
User interaction and design
...
Question | Answer | Date Answered |
---|
...
Links