Recent Releases of amphora
amphora - Release v0.10
Release notes - Amphora - Version v0.10
Bug
- [JARS-97] - When creating a dataset, description fields is required although it says it is optional
- [JARS-118] - creating snapshot: duplicate filenames clash
- [JARS-135] - resource titles should be allowed to be longer than 255 characters
- [JARS-138] - The field that stores the filename or filepath or download path is too short
- [JARS-143] - When a zotero export is uploaded, nothing is added to the collection.
Story
- [JARS-86] - Adding metadata: the entries in the dropdown box needs to indicate from which ontology they come
- [JARS-127] - Update django to 1.11
- [JARS-132] - It should be possible to check the Giles status of an upload 'by hand'
- [JARS-133] - Admins should be able to change the status of a resource by hand
- [JARS-134] - For admins the dashboard should also show upload statistics for all uploads
- [JARS-136] - It should be possible to see all resource that are part of a dataset
- JavaScript
Published by jdamerow over 7 years ago
amphora - Release v0.8
Release Notes - Amphora - Version v0.8
Bug
- [JARS-82] - Huge database latency when loading resources
- [JARS-98] - When trying to create a snapshot of a dynamic dataset, an error is shown.
- [JARS-106] - Going to the Giles log without paratemers throughs an error
- [JARS-110] - submitted files raise processing error
- [JARS-111] - Resource uploads stay in Polling state indefinitely
- [JARS-116] - Too many files in snapshot cause export to fail
- [JARS-119] - Since duplicated resources are created, the get by URI function fails
- [JARS-120] - When retrieving a resource by it's URI, authentication fails.
- [JARS-121] - Amphora crashes while serving large dataset zip files
- [JARS-123] - REST API based resource uploads are failing
Story
- [JARS-89] - JSTOR data need to be added to Elasticsearch and amphora
- [JARS-100] - Amphora needs to log the time of events
- [JARS-124] - Amphora should show all files that Giles generates
- [JARS-125] - The search times out
- [JARS-126] - Support Resource metadata export
- JavaScript
Published by jdamerow over 8 years ago
amphora - Release v0.7
Release notes - Amphora - Version v0.7
Bug
- [JARS-99] - When creating a snapshot of a explicit dataset, the downloaded zip doesnt contain any files
- [JARS-105] - Some texts are not displayed in VogonWeb
Story
- [JARS-91] - Document REST upload endpoint in Confluence
- [JARS-101] - It should be possible to prioritize certain upload tasks
- [JARS-109] - When creating a snapshot, Amphora times out
- JavaScript
Published by jdamerow over 8 years ago
amphora - Release v0.6
Release notes - Amphora - Version v0.6
Bug
- [JARS-84] - Users who are not added to a public collection can't see public collections in Vogon
- [JARS-88] - celery_start script needs to start one process for celery beat and an extra for workers
- [JARS-96] - Resources don't seem to follow public/non public rules
Story
- [JARS-80] - Github token authentication should cache Github responses
- [JARS-83] - There should be a functionality to define where the content of a resource starts and ends
- [JARS-90] - support resource content uploads through REST API
- [JARS-92] - Resource type field needs to be an autocomplete field
- [JARS-93] - Adding/editing metadata: predicate field needs to be an autocomplete field
- [JARS-95] - It should be possible to restart a Giles upload that failed before.
- JavaScript
Published by jdamerow over 8 years ago
amphora - Amphora version 0.5
Release Notes - Amphora - Version 0.5
Story
- [JARS-9] - When linking a conceptpower entry to a metadata entry, curator should be able to search for a conceptpower URI
- [JARS-11] - In the resource view, if a metadata entry has an associated conceptpower URI, an icon should be shown next to that entry
- [JARS-32] - In entity detail view, relations should include additional information about resources
- [JARS-49] - Users should be able to associate specific data about an entity (e.g. nationality, date of birth, etc.) from the entity detail view
- [JARS-50] - Specific data about entities should be automatically generated from VIAF results, but flagged as tentative
Task
- [JARS-27] - Clean up dependencies
- JavaScript
Published by erickpeirson about 9 years ago
amphora - Amphora version 0.4
Release Notes - JARS - Version 0.4
Bug
- [JARS-67] - Setting permissions on new resources is really slow
Story
- [JARS-75] - ConceptEntity instances should not be altered during merge; instead, we should create an identity mapping
- [JARS-77] - A resource should belong to one and only one collection
- [JARS-78] - Authorizations should be determined at the collection level only
Task
- [JARS-76] - Data migration: existing ConceptEntities that belong to multiple resources should be cloned and separated
- JavaScript
Published by erickpeirson over 9 years ago
amphora - Amphora version 0.3.2
Release Notes - JARS - Version 0.3.2
Bug
- [JARS-68] - Non-ascii characters in file names cause UnicodeDecodeError in giles.send_to_giles (line 156)
- [JARS-72] - In many views, the ID of an object is shown instead of its name
Story
- [JARS-14] - In the collection detail view, curators should be able to create sub-collections
- [JARS-63] - In collection and resource list views, should not set "created by" filter by default
- [JARS-69] - Media content should be protected by authorization checks
- [JARS-73] - When user visits resource view, should check to ensure that giles token is current
Task
- [JARS-70] - In the collection detail view, if the collection has sub-collections they should be listed
- [JARS-71] - Sub-collections should not be listed in the collection list view
- JavaScript
Published by erickpeirson over 9 years ago
amphora - Amphora version 0.3.1
Release Notes - JARS - Version 0.3.1
Bug
- [JARS-64] - Metadata relations are not properly filtered by authorization
Story
- [JARS-65] - When a file is sent to Giles, a reference to the transaction should be stored
- [JARS-66] - The number of outstanding requests to Giles should be capped
- JavaScript
Published by erickpeirson over 9 years ago
amphora - Amphora version 0.3
Release Notes - JARS - Version 0.3
Epic
- [JARS-15] - In the resource list view, curators should be able to add a resource to a collection
Bug
- [JARS-60] - When a non-previewable resource is viewed, the resource content is automatically downloaded
- [JARS-61] - Resource title is not shown in most views; only ID
- [JARS-62] - Prune relations function on conceptentity does not remove all duplicate relations
Story
- [JARS-12] - In the resource list view, the date that each resource was last updated should be displayed on the right-hand side
- [JARS-13] - In the collections list view, curators should be able to create new collections
- [JARS-16] - In the resource list view, a list of collections should be shown in a panel on the left side of the page
- [JARS-34] - When associating a Concept with a ConceptEntity, curator can search for Concepts.
- [JARS-35] - When searching for Concepts via the REST API (used by curation interface), also retrieves concepts from remote.
- [JARS-36] - Similar conceptentities are sorted by edit distance.
- [JARS-37] - Can merge all similar conceptentites.
- [JARS-38] - Can prune duplicate relations on conceptentities.
- [JARS-39] - Can view all resources related to a conceptentity given a specific predicate.
- [JARS-40] - REST API should have an endpoint for concepts
- [JARS-41] - REST API enforces authorizations at Resource and Collection level
- [JARS-42] - authorizations are enforced in entity detail and resource detail views, and in collection list view
- [JARS-43] - Permissions enforced consistently in metadata views
Task
- [JARS-55] - Write a function in the ``operations`` module that adds several resources to a collection
- [JARS-56] - The list of resources in the resource list view should be encapsulated in a form, and each resource should have a checkbox input to its left
- [JARS-57] - Add a submit button above the resource list, labeled "add to collection"
- [JARS-58] - Create a new view called "bulk_action_resource"
- [JARS-59] - Create a new view called "bulk_add_resource_to_collection"
- JavaScript
Published by erickpeirson over 9 years ago
amphora - JARS: Amphora version 0.2.4
Release Notes - JARS - Version 0.2.4
Story
- [JARS-30] - Curators should be able to merge resources
- [JARS-31] - Curator can merge all entities in a result set from the list view
- [JARS-33] - Curator can prune duplicate metadata relations from a resource
- JavaScript
Published by erickpeirson almost 10 years ago
amphora - JARS: Amphora version 0.2.3
Release Notes - JARS - Version 0.2.3
Story
- [JARS-6] - In the metadata tab of the edit view, curator should be able to click on a link icon to start associating a conceptpower entry
- [JARS-7] - In the metadata tab of the edit view, curator can click on a pencil icon to edit the freeform value for a metadata entry
- [JARS-8] - When linking a conceptpower entry to a metadata entry, curator should be able to manually enter a concept URI
- [JARS-28] - When merging concept entities, curator should be able to specify which entity is the "master" entity
- [JARS-29] - Curators should be able to edit the details of entities
- JavaScript
Published by erickpeirson almost 10 years ago
amphora - JARS: Amphora version 0.2.2
Release Notes - JARS - Version 0.2.2
Story
- [JARS-2] - In the resource list view, the creator of each resource should be shown underneath the name of the resource
- [JARS-22] - Users should be able to grant view, edit, and delete permissions to individual objects
- [JARS-23] - Users should be able to grant view, edit, and delete permissions to all objects in a collection
- [JARS-24] - Users should be able to grant add/remove permissions for collections that they own
- [JARS-25] - Curators should be able to merge conceptentities
- [JARS-26] - Users should be able to view permissions set on a specific object that they own
Task
- [JARS-3] - Clean up configurations
- JavaScript
Published by erickpeirson almost 10 years ago
amphora - JARS: Amphora version 0.2.1
Release Notes - JARS - Version 0.2.1
Story
- [JARS-1] - In the resource list view, the type of each resource should be listed next to the name of the resource
- [JARS-17] - Curators should be able to directly search metadata relations by subject, predicate, and/or object
- [JARS-18] - Users should be able to view details of ConceptEntities
- [JARS-19] - Users should be able to view a list of of ConceptEntities in the system
- [JARS-20] - User can filter entities by type
- [JARS-21] - When filtering entities and resources by type, only types that are actually instantiated should be shown
Task
- [JARS-4] - Investigate using PURL for persistance
- JavaScript
Published by erickpeirson almost 10 years ago