-
Notifications
You must be signed in to change notification settings - Fork 31
Ideas
These are the really big high-level things we'd like to work on. Some are from a tech view, some from a comics database view. Many mundane tasks are found in our issue tracker.
We are currently using Elasticsearch and MySQL-database searches. General text searches with Elasticsearch work fine. But we need easy to use and better search for field-specific data, i.e. we need to replace our Advanced Search.
The UI needs a revamp. The my.comics.org project is already using Bootstrap for the UI, and we are investigating doing the same with the main site. Other front-end technologies may be endorsed as well as we flesh out this project.
We want to create a comics bibliography module within the database to fulfill one of our stated goals: "The ability to record references to all books and articles about comics stories, strips, and panels, their creators, their publishers, or profiles or histories of comics features, characters, or publications."
The features and design of this module are under discussion by the Comics Bibliography Committee, whose draft report may provide further details.
A first stage is implemented to have corresponding about comics-sequences in publications.
We would like to build a newspaper comic strip database.
Any and all strips and cartoons from any and all local or national newspapers, including college/university newspapers and alternative newspapers, from any country, are eligible for inclusion. See the Comic Strip Committee report for more details.
We have a Bugzilla-based submission-system for errors in our database. We want to integrate that into our Django setup (using the same login) by using a suitable Django package adapted to our needs. By that, we can connect error submissions to the particular field in question, or the submitted error can appear directly as a comment in the issue in question. Further functionalities using a Django-based error tracker would need to be discussed.