Details
-
Type: Epic
-
Status: In Progress (View Workflow)
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Epic Name:Update IGB Quickload
-
Story Points:5
Description
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for this.
Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions.
Requirements:
- Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location (or new hosting) if required
- The repository should be accessible via https
- The repository should be world-readable, but only certain users should be able to write to it
- The process for adding and removing users and configuring user permissions should be well-documented
- The repository address will be under the bioviz domain (svn.bioviz.org)
The repository should contain:
- foundational gene model annotations for genomes depicting in the IGB home screen carousel
- genome sequence data in 2bit format for smaller genomes
- annots.xml and genome.txt files for genomes
- contents.xml file describe the contents of the repository
- .htaccess files configuring IGB Quickload directory listings when deployed to static content directories of Apache Web server
- up-to-date data
Data sets should be well-documented in commit messages or in files to ensure that users can easily determine where the data came from, and when.
Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented.
Documentation and code for setting up the svn repository and/or collecting data should be version-controlled in https://bitbucket.org/lorainelab/igbquickload
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Child |
|
Description |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for the server we were using to host the repository. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented The repository should contain: * foundational annotations for genomes * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings Data sets should be well-documented in commit messages to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for the server we were using to host the repository. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented The repository should contain: * foundational annotations for genomes * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings Data sets should be well-documented in commit messages to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. Documentation and code should be version-controlled in https://bitbucket.org/lorainelab/igbquickload |
Description |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for the server we were using to host the repository. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented The repository should contain: * foundational annotations for genomes * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings Data sets should be well-documented in commit messages to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. Documentation and code should be version-controlled in https://bitbucket.org/lorainelab/igbquickload |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for this. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location (or new hosting) if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented * The repository address will be under the bioviz domain (svn.bioviz.org) The repository should contain: * foundational gene model annotations for genomes depicting in the IGB home screen carousel * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings when deployed to static content directories of Apache Web server Data sets should be well-documented in commit messages to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. Documentation and code for setting up the svn repository and/or collecting data should be version-controlled in https://bitbucket.org/lorainelab/igbquickload |
Summary | Migrate IGB Quickload data repository to svn on EC2 | Update IGB Quickload |
Description |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for this. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location (or new hosting) if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented * The repository address will be under the bioviz domain (svn.bioviz.org) The repository should contain: * foundational gene model annotations for genomes depicting in the IGB home screen carousel * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings when deployed to static content directories of Apache Web server Data sets should be well-documented in commit messages to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. Documentation and code for setting up the svn repository and/or collecting data should be version-controlled in https://bitbucket.org/lorainelab/igbquickload |
For many years, we used a subversion repository hosted at UNC Charlotte to maintain and mirror foundational data sets used by IGB.
In 2017, UNC Charlotte stopped providing support for this. Now, we need to set up our own svn hosting using Amazon Web services. At the same time, we need to update the data files to the most recent versions. Requirements: * Procedures to set up and configure the subversion repository should be well-documented to ensure that we can easily migrate the repository to a new location (or new hosting) if required * The repository should be accessible via https * The repository should be world-readable, but only certain users should be able to write to it * The process for adding and removing users and configuring user permissions should be well-documented * The repository address will be under the bioviz domain (svn.bioviz.org) The repository should contain: * foundational gene model annotations for genomes depicting in the IGB home screen carousel * genome sequence data in 2bit format for smaller genomes * annots.xml and genome.txt files for genomes * contents.xml file describe the contents of the repository * .htaccess files configuring IGB Quickload directory listings when deployed to static content directories of Apache Web server * up-to-date data Data sets should be well-documented in commit messages or in files to ensure that users can easily determine where the data came from, and when. Procedures for using subversion to "check out" and update copies of the repository into Web directories for IGB access should be clearly documented. Documentation and code for setting up the svn repository and/or collecting data should be version-controlled in https://bitbucket.org/lorainelab/igbquickload |
Epic Name | Migrate IGB Quickload data repository to svn on EC2 | Update IGB Quickload |
Epic Child |
|
Epic Status | To Do [ 10001 ] | Done [ 10003 ] |
Epic Child |
|
Epic Child | IGBF-1524 [ 17610 ] |
Workflow | Loraine Lab Workflow [ 18099 ] | Fall 2019 Workflow Update [ 18901 ] |
Workflow | Fall 2019 Workflow Update [ 18901 ] | Revised Fall 2019 Workflow Update [ 21028 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Epic Child | IGBF-1524 [ 17610 ] |
Epic Child |
|
Epic Child |
|
Epic Child | IGBF-1122 [ 17058 ] |
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Name | Update IGB Quickload | Support tardigrade genome assemblies and rna-seq in IGB |
Epic Name | Support tardigrade genome assemblies and rna-seq in IGB | Update IGB Qjuickload |
Epic Name | Update IGB Qjuickload | Update IGB Quickload |
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Child |
|
Epic Child |
|