Details
-
Type: New Feature
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:3
-
Epic Link:
-
Sprint:Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct, Fall 3: Oct 12 - Oct 23
Description
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories."
These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database.
Curated categories will themselves be grouped into curated category types.
For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search"
Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed.
Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu"
Thoughts on implementation:
- Determine the best way to add this new kind of "curated category" to the code base
- To avoid making our existing Django app folders even more heinously complicated, can introduces this as a (mostly) stand-alone Django app "curated_categories" with its own models.py file and so forth?
- Don't muck about with the existing "user provided" App categories. Ignore this for now.
- Curated categories can have foreign keys to IGB apps, but not the other way around.
Once this is fully implemented, we will make changes to the user interface. We will create a home page that shows a hyperlinked listing of "curated category types" and the "curated categories" beneath them. When uses click on an entry in this listing, a filter will be applied that shows just the apps that the selected entry points to.
As always, before implementing this functionality, search Django world for Django apps with related functionality.
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1388 [ 17463 ] |
Description |
Currently, App developers can create new categories that then are displayed in various locations.
Instead, the App Store hosting group should provide a curated listing of categories that are provisioned as part of the app store setup process. These should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired category will need to be updated in the database. Also, there will be categories of categories, also defined in the code base. * "Biology" categories describe what type of scientific utility an App has Examples) Homology search, Epigenetics, ChIP-Seq * "IGB interface" categories describe what part of the IGB interface gets changed by installing the App Examples) Tools menu, Right-click menu, New tab |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to thie curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" |
Description |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to thie curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" |
Description |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" Thoughts on implementation: * Determine the best way to add this new kind of "curated category" to the code base * To avoid making our existing Django app folders even more heinously complicated, can introduces this as a (mostly) stand-alone Django app "curated_categories" with its own models.py file and so forth? * Don't muck about with the existing "user provided" App categories. Ignore this for now. * Curated categories can have foreign keys to IGB apps, but not the other way around. Once this is fully implemented, we will make changes to the user interface. We will create a home page that shows a hyperlinked listing of "curated category types" and the "curated categories" beneath them. When uses click on an entry in this listing, a filter will be applied that shows just the apps that the selected entry points to. |
Description |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" Thoughts on implementation: * Determine the best way to add this new kind of "curated category" to the code base * To avoid making our existing Django app folders even more heinously complicated, can introduces this as a (mostly) stand-alone Django app "curated_categories" with its own models.py file and so forth? * Don't muck about with the existing "user provided" App categories. Ignore this for now. * Curated categories can have foreign keys to IGB apps, but not the other way around. Once this is fully implemented, we will make changes to the user interface. We will create a home page that shows a hyperlinked listing of "curated category types" and the "curated categories" beneath them. When uses click on an entry in this listing, a filter will be applied that shows just the apps that the selected entry points to. |
Currently, App developers can create new categories that then are displayed in various locations.
This is fine, but we also need a new kind of "curated category" that app store maintainers provide and curate over time. Users will be able to associate their Apps with "curated categories" but will not be able to create new "curated categories." These "curated categories" should be stored in an easy-to-edit file within the code base. When app stores are deployed or updated, these curated categories need to be added or updated within the code base accordingly. The add-and-update process must also be intelligent enough to remove categories that become obsolete. This means that any existing App that has a retired "curated category" will need to be updated in the database. Curated categories will themselves be grouped into curated category types. For example - "scientific application" is a "curated category type". Examples of "curated categories" belonging to the curated category type of "scientific application" could include "ChIP-Seq" and "RNA-Seq" and "epigenetics" and "homology search" Another "curated category type" is "IGB interface," which refers to the part of the IGB user interface that gets enhanced when the App is installed. Examples of "IGB interface" curated categories include: "Adds a tab" and "Tools menu" Thoughts on implementation: * Determine the best way to add this new kind of "curated category" to the code base * To avoid making our existing Django app folders even more heinously complicated, can introduces this as a (mostly) stand-alone Django app "curated_categories" with its own models.py file and so forth? * Don't muck about with the existing "user provided" App categories. Ignore this for now. * Curated categories can have foreign keys to IGB apps, but not the other way around. Once this is fully implemented, we will make changes to the user interface. We will create a home page that shows a hyperlinked listing of "curated category types" and the "curated categories" beneath them. When uses click on an entry in this listing, a filter will be applied that shows just the apps that the selected entry points to. As always, before implementing this functionality, search Django world for Django apps with related functionality. |
Assignee | Ann Loraine [ aloraine ] |
Summary | Refactor App Store to use curated categories | Add curated categories and curated category types to App Store codebase |
Assignee | Sameer Shanbhag [ sameer ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Sprint | Summer 6: 17 Aug - 28 Aug [ 101 ] | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 101, 102 ] |
Rank | Ranked higher |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Assignee | Sameer Shanbhag [ sameer ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Assignee | Ann Loraine [ aloraine ] |
Assignee | Ann Loraine [ aloraine ] | Sameer Shanbhag [ sameer ] |
Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
Sprint | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep [ 101, 102 ] | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep [ 101, 102, 103 ] |
Rank | Ranked higher |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Assignee | Sameer Shanbhag [ sameer ] | Ann Loraine [ aloraine ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
Assignee | Ann Loraine [ aloraine ] | Sameer Shanbhag [ sameer ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Sprint | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep [ 101, 102, 103 ] | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct [ 101, 102, 103, 104 ] |
Rank | Ranked higher |
Assignee | Sameer Shanbhag [ sameer ] |
Sprint | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct [ 101, 102, 103, 104 ] | Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct, Fall 3: Oct 12 - Oct 23 [ 101, 102, 103, 104, 106 ] |
Rank | Ranked higher |
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Assignee | Sameer Shanbhag [ sameer ] |