Releases: diging/vogon-web
Releases · diging/vogon-web
VogonWeb Release v0.8
VogonWeb Release v0.7
VogonWeb v0.6
Release notes - VogonWeb - Version v0.6
Sub-task
- [VGNWB-21] - If the text is a file that the user uploaded, it should be added to JARS as a LocalResource along with the file itself
- [VGNWB-22] - If the text is added from a URL, it should be added to JARS as a RemoteResource
- [VGNWB-30] - Update user of disposition of the file
Bug
- [VGNWB-210] - In list of annotations: next link does not care about filters
- [VGNWB-211] - Creating new templates doesn't work
- [VGNWB-212] - Vogon text annotations for the first word in an article are unsuccessful
- [VGNWB-213] - Resolving concepts: exception because label and uri are blank
- [VGNWB-215] - Error during template rendering/404 Not Found when trying to load "Matthew's Embryo Project"
- [VGNWB-217] - Submitting relationships to Quadriga doesn't work
- [VGNWB-218] - Templates with more than two relations create an excessive amount of relations
- [VGNWB-220] - Date appellations don't seem to work
- [VGNWB-223] - On concept list, filters get lost when going to the next page
- [VGNWB-224] - For some reason, after adding a text to a project, the text shows up twice
- [VGNWB-226] - The relations that are shown for a text on the right side can't be scrolled if there are too many
- [VGNWB-229] - Creating relations: when a wordnet concept is selected, the field stays blank after selecing
- [VGNWB-230] - The "Take me back" button on the concept add view doesn't work.
- [VGNWB-231] - Documents from Embryo Project not appearing in VogonWeb
Story
VogonWeb version 0.5
Release Notes - VogonWeb - Version 0.5
Epic
- [VGNWB-37] - VogonWeb should communicate with JARS
Bug
- [VGNWB-154] - Sometimes when creating a new appellation from the relation creation workflow, two modals are opened instead of just one
- [VGNWB-176] - When a user creates a new concept while appellating, the new appellation does not appear in the list of appellations
- [VGNWB-193] - Evidence only allows one word
- [VGNWB-201] - When a user annotates a text for the first time, the graph view is not populated as the user creates relations
- [VGNWB-204] - New appellations don't visibly appear to be created
- [VGNWB-205] - Apellations are deleted from the article
- [VGNWB-206] - New VogonWeb annotation interface doesn't seem to show all annotations
- [VGNWB-208] - Templates can't be filled in (or I don't understand how)
Story
- [VGNWB-3] - When a user tries to add a text, they should be guided through the process one step at a time
- [VGNWB-5] - Users should be able to select texts to annotate from collections in JARS
- [VGNWB-6] - Users should be able to log in using Facebook
- [VGNWB-7] - Users should be able to log in using Github
- [VGNWB-9] - Users should be able to add texts that they have annotated to collections
- [VGNWB-13] - If a text is flagged as private, an administrator should be able to grant individual users access to the text
- [VGNWB-17] - Documents added from the web should sanitized and prepped for annotation
- [VGNWB-19] - An administrator should be able to add JARS instances for managing texts
- [VGNWB-20] - When a text is added by a user (either by uploading or by entering a URL), it should be added to the default JARS instance
- [VGNWB-25] - Users should see how many created relations for each text have not yet been committed to QStore
- [VGNWB-72] - Annotations that have been accessioned to QStore4s should be assigned an accession ID (from QStore4s)
- [VGNWB-74] - User should be able to hide/unhide annotations that have already been accessioned to QStore4s
- [VGNWB-115] - Delete options on two articles should be aligned with others
- [VGNWB-132] - Types when creating a new appellation should be sorted numerically
- [VGNWB-142] - In the REST API, should be able to filter appellations by text URI
- [VGNWB-149] - If a text is not public, participants in the collection to which that text belongs should be able to annotate the text
- [VGNWB-153] - When creating a new relationtemplate, should be able to indicate that a node is/is not a terminal node
- [VGNWB-182] - Integrate webpagedump into ingestion system
- [VGNWB-185] - There should only be one "Robert Chambers" appellation
- [VGNWB-186] - The article's author should be displayed near the title
- [VGNWB-189] - Relation Templates should include mapping to triple representation
- [VGNWB-191] - Users should be able to add texts from a variety of different repositories
- [VGNWB-192] - Administrators should be able to configure external repositories without writing new code
- [VGNWB-195] - Users should be able to annotate images
- [VGNWB-196] - Users should be able to annotate rendered web pages (without scraping content)
Task
- [VGNWB-69] - "Collections" should be replaced with "Projects"
- [VGNWB-97] - Add Firefox support for annotation interface
- [VGNWB-99] - User should be able to search for texts by author
- [VGNWB-188] - Data model should support authors
- [VGNWB-197] - Extend snippet-building functions to support image annotations
- [VGNWB-198] - Extend snippet-building functions to support webpage annotations
- [VGNWB-199] - Extend quadruple-building functions to support image annotations
- [VGNWB-202] - Implement POST methods for repositories
- [VGNWB-203] - Implement some kind of all-purpose authentication mechanism for repositories
VogonWeb v0.4
Release Notes - VogonWeb - Version 0.4
Story
- [VGNWB-11] - Users should be able to see other users' collections
- [VGNWB-31] - Users should be able to commit annotations to QStore for a single text or a collection
- [VGNWB-32] - Relations should be transformed to Quadruple XML for addition to QStore
- [VGNWB-41] - Concepts in annotations that are submitted to QStore4s must be added to Conceptpower first
- [VGNWB-63] - When a user submits a network from Vogon Web, Quadriga should create a project if it doesnt exist yet.
VogonWeb v0.3.3
VogonWeb v0.3.1
Release Notes - VogonWeb - Version 0.3.1
Sub-task
- [VGNWB-162] - On the concept detail view, the textual basis (stringRep) for each appellation should be shown.
- [VGNWB-163] - On the concept detail view, The layout should have two columns, with the label/description on the left, and appellations on the right.
- [VGNWB-164] - On the concept detail view, add a panel that shows related concepts.
- [VGNWB-166] - The relations view should have two columns
- [VGNWB-167] - The relations view should show details about each RelationSet involving the selected concepts
- [VGNWB-168] - The relations view should have a panel for each of the two concepts, with details about each concept
- [VGNWB-180] - Create a new view that returns appellation data for a given concept
- [VGNWB-181] - On the front page, bind a listener to the node select event
Bug
- [VGNWB-151] - Unable to create collection in the dashboard page
- [VGNWB-169] - When user submits their profile form, the value for the "link" field is not updated in the database
- [VGNWB-178] - Article is interesting and easy to appellate, plus...
Story
- [VGNWB-12] - Texts should be flagged as either public or private
- [VGNWB-24] - Users should be able to see the number of relations that they have created for each text
- [VGNWB-34] - Users should be able to see a network visualization of relations, filtered by text, text collection, concept type(s), relation type(s), and/or user(s)
- [VGNWB-35] - Users should be able to see the annotations that other users have made for a text
- [VGNWB-111] - The boxes that come up when adding appellations/relations be movable in order to read the text and add the relevant information simultaneously
- [VGNWB-134] - When an anonymous user accesses a text, they should see a network representation of the relations on the page
- [VGNWB-136] - When an anonymous user views a text, they should see a list of relations for that text
- [VGNWB-137] - On the text page, when a user clicks on a relation they should see the text passage for that relation
- [VGNWB-161] - Concept detail view should be reorganized and improved
- [VGNWB-165] - Improvements to the relations view
- [VGNWB-179] - On the front page, when a user clicks on a node, the texts in which that concept occurs should be shown, along with a snippet of text showing the appellation
Task
VogonWeb v0.3: Introducing search!
Release Notes - VogonWeb - Version 0.3
Sub-task
- [VGNWB-146] - When the user submits the merge concept form, the source concepts should be updated to point to the target concept
Epic
- [VGNWB-145] - Epic branch for accomplishing elastic search functionality.
Bug
- [VGNWB-143] - Major memory leak
- [VGNWB-170] - When you create an appellation VogonWeb doesn't let you make another unless the page is refreshed
Story
- [VGNWB-46] - An administrator should be able to merge two concepts
- [VGNWB-60] - When a Concept is added from a remote authority (e.g. Conceptpower), its state should be RESOLVED
- [VGNWB-95] - Users should be able to search (text contains) for texts in the text list view
- [VGNWB-123] - Install Haystack and configure for use with elasticsearch
- [VGNWB-135] - Users should see a stream with a summary of recent activity
- [VGNWB-147] - The owner of a collection should be able to add participants to that collection
- [VGNWB-148] - The owner of a collection should be able to remove participants from that collection
- [VGNWB-150] - On the contributor view, a graph of user contributions over time should be displayed
- [VGNWB-172] - There should be a page that defines 'types' for new appellations