ace issueshttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues2017-12-06T11:42:16-05:00https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/45Deploy to Obj from pipeline2017-12-06T11:42:16-05:00Ghost UserDeploy to Obj from pipelineWe can streamline our deploy process a bit more to include creating our release artifacts for us and pushing them to obj. Since this is all cli based, we should be able to update the .gitlab-ci.yml in order to accomplish this.
The files...We can streamline our deploy process a bit more to include creating our release artifacts for us and pushing them to obj. Since this is all cli based, we should be able to update the .gitlab-ci.yml in order to accomplish this.
The files needed to be uploaded are
* ace-$VERSION-src.tar.gz
* ace-dist-$VERSION-RELEASE-bin.tar.gz
* ace-dist-$VERSION-RELEASE-bin.ziphttps://gitlab.umiacs.umd.edu/adapt/ace/-/issues/34Paginated pull of content in Browse Servlet2018-01-23T08:32:46-05:00Ghost UserPaginated pull of content in Browse ServletIn the browse servlet, folders with a large number of items can cause the Audit Manager to choke while it fetches everything from the database. We should aim to pull only a subset of items at a time.In the browse servlet, folders with a large number of items can cause the Audit Manager to choke while it fetches everything from the database. We should aim to pull only a subset of items at a time.https://gitlab.umiacs.umd.edu/adapt/ace/-/issues/60Servlet for Active Audits/Token Imports2019-04-04T14:23:38-04:00Ghost UserServlet for Active Audits/Token ImportsIn the ACE AMs for the Chronopolis Project, we've been ingesting large amounts of collections. We've noticed recently when trying to browse it is difficult to find out which collections are actively auditing, and it's almost impossible t...In the ACE AMs for the Chronopolis Project, we've been ingesting large amounts of collections. We've noticed recently when trying to browse it is difficult to find out which collections are actively auditing, and it's almost impossible to see what collections are ingesting tokens.
Given that these both use the same thread pool, as they are processes which modify collections, it would be nice to have a servlet which can show any active processes. We will probably want to show information from the audit/token ingest when browsing the collections in this servlet. Maybe retrieving information from the CollectionThreadPoolExecutor. As this is still in its conception, nothing is really set in stone yet.