List view
The goal is to update our model for schemas and associated mappings, create an endpoints and UI to manage them.
Due by February 19, 2019All tasks mainly related to deliver the ATLAS Demo. + some leftovers from the previous sprint.
Due by January 25, 2019•9/9 issues closed- Due by December 18, 2018•12/12 issues closed
Stabilisation and consolidation for Beta release.
Due by November 12, 2018•16/16 issues closedThings that has to be done before CAP Beta release. Mind map available here: https://drive.google.com/file/d/1WKkJmpbWN2qgWs7rwwKxUBELF8uO6ARx/view?usp=sharing
Due by October 31, 2018•100/100 issues closedRelated issue in COD: #2419
Due by September 30, 2018•1/1 issues closedDemonstrate the reuse of an analysis deposited on CAP by rerunning it on a REANA instance. In CAP, introduce “rerun” tab, show progress status, show final plots. In REANA, accept payload from CAP, expose progress status and logs, expose final plots. Example: ALICE LEGO train test run and validation and histogram plot production.
Due by June 20, 2018•2/2 issues closedStabilisation and clean up after workshop.
Due by July 2, 2018•11/11 issues closed- Due by June 11, 2018•18/18 issues closed
- Due by May 7, 2018•9/9 issues closed
We want to demonstrate interesting search capabilities on ingested information from existing collaboration sources, like e.g. CADI database. To reach this we need to ingest CMS analyses from CADI, add information about data samples and triggers used (Rishika), final state particles (Kati). We want to provide rich search query examples, e.g. which analyses used such-and-such MC sample or such-and-such HLT trigger.
Due by April 20, 2018•10/10 issues closed- Due by March 18, 2018•11/11 issues closed
One week sprint to finish leftovers from previous ones, e.g. CAP client and its integration. The only new tasks for this sprint are: - daily synchronize CMS analysis with CADI database, add prompt to inform users about changes Sprint leader: Pamfilos
Due by March 9, 2018•31/31 issues closed- No due date•10/10 issues closed
Finalize connection, authentication, content ingestion and autocomplete. Investigate best solution, e.g. updates by CADI every night? Definition of done: testable (including autocomplete) by users. First tests by Sebastian.
Due by December 1, 2017•6/6 issues closedFinalize creating the code importer library that accepts GitLab/GitHub URI and would import a tarball corresponding to given SHA1 or tag. Discuss and solve implementation (skopeo/dockerpy) and authentication. Serializer: merge PRs, get documentation done, stabilize Client: permissions, refactoring [resolve RFC], tests Sprint leader: Ioannis
Due by February 9, 2018•8/8 issues closedCreate a code importer library that would accept GitLab/GitHub URI and would import a tarball corresponding to given SHA1 or tag. (PULL) Enrich cap-client to be able to submit code files (PUSH) Common milestone with https://github.com/cernanalysispreservation/cap-client/milestone/2
Due by October 20, 2017•6/6 issues closed- No due date•1/1 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
- No due date•3/3 issues closed
- No due date•3/3 issues closed
Mirroring Deposit UI functionality to the API
No due date•16/16 issues closedImplement testing for various features of instance
No due date•1/1 issues closedFinalise schemas and investigate/introduce JSON-LD
No due date•8/8 issues closedCreating a useful and convenient "detailed" view page for records
No due date•5/5 issues closedImplementing UI towards the designs given
No due date•48/48 issues closedglobal changes to user interface to enable user interaction and improve the user experience
Due by October 30, 2016•3/3 issues closediterative improvement during autumn 2016
Due by October 31, 2016•1/1 issues closediterative improvement during autumn 2016
Due by October 30, 2016•8/8 issues closed- No due date•4/4 issues closed
- Due by July 26, 2016•7/7 issues closed
Nicer UI with search.
Due by August 30, 2016•3/3 issues closedAdditional features (access control, alerts, HyperNews).
Due by May 30, 2016tasks and (external) dependencies for a release prototype
No due date•5/5 issues closedtasks and (external) dependencies for a release prototype
No due date•14/14 issues closedtasks and (external) dependencies for a release prototype
No due date•2/2 issues closedSystem operation matters towards future production
No due date•25/25 issues closed- Due by October 23, 2015•6/6 issues closed
tasks and (external) dependencies for a release prototype
No due date•30/30 issues closedMinimal viable product.
Due by May 30, 2016•14/14 issues closed