| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | REST API | Angular UI | |||||||||||||||||||||||
2 | Category | Final Priority | Feature | Specs / Notes | Mid Estimate (Hours) | Status | Specs / Notes | Mid Estimate (Hours) | Status | ||||||||||||||||
3 | SEO | Robots.txt for SEO | 0 | (not applicable) | Add a default robots.txt to Angular UI source | 6 | 3. ready to be worked on | ||||||||||||||||||
4 | SEO | Sitemaps for SEO | DS-4061 | 5 | 3. ready to be worked on | Sitemap content must appear off root path of UI (like robots.txt) | 2 | 1. needs ticket(s) | |||||||||||||||||
5 | UI | New Theme for User Interface | TBD | (not applicable) | Mantis is the initial theme. This is not necessarily done until we are "feature complete" (ongoing work). This was initially about hiring a designer for another theme (4Science is still interested in helping fund a professional designer with others) | TBD | |||||||||||||||||||
6 | UI | Support separate themes per community or collection (like XMLUI) | 0 | (not applicable) | Sitewide themes is done (see OR2019 workshops). Community/Collection specific theming is more difficult until we upgrade Angular 8. | TBD | 1. needs ticket(s) | ||||||||||||||||||
7 | Security | Upgrade to Angular 8 | 0 | (not applicable) | Requires senior developer - follow the angular update guide, from 6 to 7, complexity advanced, using yarn - upgrade outdated dependencies in package.json using yarn upgrade-interactive - fix any issues with dependencies that don't have a compatible version, or swap out dependencies if necessary | 60 | 3. ready to be worked on | ||||||||||||||||||
8 | Security | Upgrade to Angular 9 | 0 | (not applicable) | Angular 9 is not yet released. | 40 | |||||||||||||||||||
9 | Admin | The harvesting client (XMLUI only) should be ported to dspace 7 (https://wiki.duraspace.org/dsdoc6x/using-dspace/exporting-content-and-metadata/oai#OAI-OAI-PMH/OAI-OREHarvester(Client)) | REST endpoints already complete: https://github.com/DSpace/DSpace/pull/2491 | 0 | 6. draft implementation | This includes ability to kick off harvest from collection level and site level harvesting status (XMLUI Control Panel). We currently don't have the REST for the Control Panel. Done: - The content source tab on the edit collection page has been added an allows you to configure the params and store them to the server Still to do: - Start harvesting and show the status Specs: - Add UI elements to start a harvest and show the status - Start jobs using the scripts&processes endpoint - Get the status from the collection /harvest endpoint | 24 | 1. needs ticket(s) | |||||||||||||||||
10 | Performance | REST API Projections | https://jira.duraspace.org/browse/DS-3533 Additional options presented by Chris W on Oct 17: https://wiki.duraspace.org/display/DSPACE/2019-10-17+DSpace+7+Working+Group+Meeting | TBD | 4. in progress | Chris presented on Oct 17, 2019 meeting | TBD | 1. needs ticket(s) | |||||||||||||||||
11 | Submission | Live import framework https://wiki.duraspace.org/display/DSDOC6x/2016+Framework+for+live+import+from+external+sources | Please note that the new submission UI supports the BTE framework, see point 5.8 & 5.9 that currently provide more end user features and connectors that the custom dspace framework (AB). Early REST Contract work: https://github.com/DSpace/Rest7Contract/pull/83 | TBD | 4. in progress | TBD | |||||||||||||||||||
12 | REST | Documentation framework for the REST API (RestDoc) | https://jira.duraspace.org/browse/DS-3484 | TBD | 2. backlog (temporarily on hold) | 0 | (not applicable) | ||||||||||||||||||
13 | REST | ALPS Support | https://jira.duraspace.org/browse/DS-3486 | TBD | 2. backlog (temporarily on hold) | 0 | (not applicable) | ||||||||||||||||||
14 | Docs | Documentation of DSpace 7, especially new UI, Install & Upgrade | https://wiki.duraspace.org/display/DSDOC7x/ | TBD | 3. ready to be worked on | TBD | 3. ready to be worked on | ||||||||||||||||||
15 | Browse | Breadcrumbs in header | Depends on REST Projections? See: https://jira.duraspace.org/browse/DS-3532 | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
16 | SEO | Meta "generator" tag in page header (<meta name="Generator" content="DSpace [version]"/>) | Finalized ticket: https://jira.duraspace.org/browse/DS-4357 | 2 | 3. ready to be worked on | Use/Update metadata.service.ts? | 3 | 3. ready to be worked on | |||||||||||||||||
17 | UI | Contextual Help | New user documentation accessible linkable from the specific feature | 0 | (not applicable) | TBD | 1. needs ticket(s) | ||||||||||||||||||
18 | Auth | Protected metadata and information | Some information in the item, workspace, etc. contains sensitive / reserved information (dc.description.provenance, submitter, etc). We need to serialize the objects according to the user rights | TBD | TBD | ||||||||||||||||||||
19 | UI | Feedback Form | Form to provide feedback to the dspace administrator | TBD | TBD | ||||||||||||||||||||
20 | Security | JDK 11 Support for backend (REST API) | JDK 8 is nearing EOL. https://jira.duraspace.org/browse/DS-4380 | TBD | 3. ready to be worked on | 0 | (not applicable) | ||||||||||||||||||
21 | Browse | Browse by Community/Collection | Depends on Projections (1.12)? | 0 | 7. completed | TBD | 1. needs ticket(s) | ||||||||||||||||||
22 | Browse | RSS/ATOM Feeds | See https://jira.duraspace.org/browse/DS-3947. RSS needs to create a link based on the Angular UI (for details of the item). REST needs to translate the URL to the Angular Path (Similar idea on Sitemaps too). RSS/ATOM feeds already provided via OpenSearch, which can limit by Community or Collection. These estimates assume we will use OpenSearch and simply document the proper queries to run in different scenarios. | 2 | 3. ready to be worked on | RSS content must appear off root path of UI (like robots.txt & sitemaps). "- Proxy the backend's RSS feeds on the express.js server - Add/adapt service to retrieve RSS config from backend (e.g. whether or not it's enabled) - Add RSS buttons to the UI if it's enabled - Backend needs to be determined (might be content negiotiation on the search/discovery endpoint). Once figured out, might become more certain." | 8 | 1. needs ticket(s) | |||||||||||||||||
23 | Browse | Support Handle.net URIs | 0 | 7. completed | Senior developer required see https://github.com/DSpace/dspace-angular/issues/256 | 23 | 5. awaiting review | ||||||||||||||||||
24 | Browse | OpenURL Support | See https://jira.duraspace.org/browse/DS-4319. Assume we are only building a URL based on configuration and metadata. Reuse code from the JSPUI 6 Tag implementation adding the extra link when appropriate in the ItemResource (revisit later if needed) | 5 | 3. ready to be worked on | Links should appear on Item pages when enabled. Estimate is for just displaying embedded links if configuration is enabled. | 2 | 3. ready to be worked on | |||||||||||||||||
25 | Browse | Configurable browse | The /api/discover/browses endpoint returns the list of configured browses | 0 | 7. completed | Already COMPLETE? https://github.com/DSpace/dspace-angular/issues/259 | 0 | 5. awaiting review | |||||||||||||||||
26 | Browse | Tag Cloud visualization | Feature introduced in version 5 JSPUI, see https://jira.duraspace.org/browse/DS-1227 | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
27 | Search | OpenSearch API | See https://jira.duraspace.org/browse/DS-4249. Implement a redirect to a configurable UI search URL | 2 | 3. ready to be worked on | Just needs an HTML <head> section for Angular for autodiscovery. See http://www.opensearch.org/Specifications/OpenSearch/1.1/Draft_5#Autodiscovery_in_HTML.2FXHTML Add these tags using the metadata service | 2 | 3. ready to be worked on | |||||||||||||||||
28 | Search | Support for controlled-vocabulary - Hierarchical facets? | NEEDS VOLUNTEER | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
29 | Authentication | Authentication via Shibboleth | 0 | 6. draft implementation | https://github.com/DSpace/dspace-angular/pull/429 (NEARLY COMPLETE) | 0 | 4. in progress | ||||||||||||||||||
30 | Authorization | Authorization as someone without special rights | Needs testing | TBD | 3. ready to be worked on | Discuss how to achieve in Angular | TBD | 1. needs ticket(s) | |||||||||||||||||
31 | Authorization | Authorization as someone with Submitter rights | See https://jira.duraspace.org/browse/DS-4043 Task is to build detailed ITs (very core piece here) and verify everything is working. However, it's likely some ITs will fail initially. Lots of uncertainty here | 26 | 3. ready to be worked on | Discuss how to achieve in Angular | TBD | 1. needs ticket(s) | |||||||||||||||||
32 | Authorization | Authorization as someone with Collection Admin rights | Needs testing | TBD | 2. backlog (temporarily on hold) | Discuss how to achieve in Angular | TBD | 1. needs ticket(s) | |||||||||||||||||
33 | Authorization | Authorization as someone with Community Admin rights | Needs testing | TBD | 2. backlog (temporarily on hold) | Discuss how to achieve in Angular | TBD | 1. needs ticket(s) | |||||||||||||||||
34 | Authorization | Authorization as someone with Full Admin rights | Needs testing | TBD | 3. ready to be worked on | TBD | 1. needs ticket(s) | ||||||||||||||||||
35 | Authorization | Ensure submitters can only edit metadata fields configured in submission forms | https://jira.duraspace.org/browse/DS-4278 | TBD | 3. ready to be worked on | TBD | 1. needs ticket(s) | ||||||||||||||||||
36 | Authorization | Ensure workflow members can only perform actions assigned | https://jira.duraspace.org/browse/DS-4279. Expose the right actions for the specific workflow step (approve, reject, edit, vote, etc.) | TBD | 3. ready to be worked on | TBD | 1. needs ticket(s) | ||||||||||||||||||
37 | Account Profile | Manage Account Profile | DS-4062 | 0 | 7. completed | - Create a service to fetch and store the info - Create the form to show and modify the info | 15 | 1. needs ticket(s) | |||||||||||||||||
38 | Account Profile | Manage Subscriptions | Allow users to subscribe to Collections for daily emails. Extra subscription endpoint (subscription resource) which maps to the subscription table. May be a subresource of user. UNCERTAIN | 16 | 1. needs ticket(s) | - Create a service to retrieve, add, remove subscriptions on REST - Add the ability to subscribe/unsubscribe on the collection page itself - show an overview of active subscriptions on the profile page with the ability to remove them | 13 | 1. needs ticket(s) | |||||||||||||||||
39 | Account Profile | View Authorization Groups | https://jira.duraspace.org/browse/DS-3736 (Dependent on Account Profile, DS-4062) | 0 | 7. completed | - Create/modify a service to be able to retrieve the groups for the current user - List them on the profile page | 5 | 1. needs ticket(s) | |||||||||||||||||
40 | Account Profile | Change Password | DS-4062 | 0 | 7. completed | - Modify the authentication service to be able to change the password - Create the change password form - Add validation to ensure it follows the criteria Note, we should update those criteria: 6 characters long isn't very safe | 7 | 1. needs ticket(s) | |||||||||||||||||
41 | Authorization | Enforce Community/Collection Access Restrictions | https://jira.duraspace.org/browse/DS-4122, According to the ticket this is only about providing the testing and eventually fix misbehavior on single communities/collections but we need to filter also subcommunities and collections referenced from the object. This would require rewrite the strategy used to retrieve the children moving to a solr based approach and a LinkRestRepository. | 26 | 3. ready to be worked on | 0 | (not applicable) | ||||||||||||||||||
42 | Authorization | Enforce Item Access Restrictions | https://jira.duraspace.org/browse/DS-4123. This is just ITs | 6 | 3. ready to be worked on | 0 | (not applicable) | ||||||||||||||||||
43 | Authorization | Enforce Bitstream Access Restrictions | https://jira.duraspace.org/browse/DS-4124. Again, just ITs, although in two areas: Content Controller and BitstreamRestRepository | 8 | 3. ready to be worked on | 0 | (not applicable) | ||||||||||||||||||
44 | Account Profile | New user registration | See https://jira.duraspace.org/browse/DS-4027. Andrea feels ticket doesn't have enough info. Not just about create EPerson. Need to apply for registration, get a token and then confirm registration data. Likely needs to be two REST endpoints. Andrea feels "We should explore a solution based on posting the uri of the token to the eperson endpoint plus a json describing the registration data or create a special authentication to use the registration token as auth-token or collect all the necessary information in the registration data and move them later to the eperson" May need feedback from GDPR Working Group on whether DSpace 6 way of doing this is GDPR compliant. MOVE TO 20 hours and UNCERTAIN. NEEDS MORE DETAILED DISCUSSION TO FINALIZE. | 20 | 3. ready to be worked on | - Modify the authentication service to be able to - enter a new email for verification - use a verification token and a filled in form (at least name and password) to create a new eperson, and immediately log in - Create the user registration component, that has the 3 steps (email, profile, finished) and can be rendered in the dropdown or as a standalone page - Add links to registration to the login component | 18 | 1. needs ticket(s) | |||||||||||||||||
45 | Submission | Submission Configuration Upgrade script (input-forms to submission-forms) | https://jira.duraspace.org/browse/DS-4046. Currently, estimate assumes we need to do this migration via Java code (Generate a submission form where each inputform step is mapped to a single panel. It includes also the generation of a new item-submissions where the single panel are listed). However, we might be able to cut the effort in half if we can simply use an XSLT transformation (as both files are XML) | 22 | 3. ready to be worked on | 0 | (not applicable) | ||||||||||||||||||
46 | Submission | Submission via an identifier | The submission PR includes the capabilities to enrich the submission with information retrieved by the bibliographic database once than an identifier is provided. This is slightly different than the current JSPUI functionality "Search by Identifiers". We are interested in implement also this functionality but it has a very low priority and could IMHO eventually excluded from DSpace 7 - ab | TBD | 2. backlog (temporarily on hold) | TBD | 1. needs ticket(s) | ||||||||||||||||||
47 | Submission | Support for authority framework | https://jira.duraspace.org/browse/DS-4350 | TBD | 3. ready to be worked on | 0 | 6. draft implementation | ||||||||||||||||||
48 | Submission | Embargo Item Metadata | Embargo bitstream already exists (REST contract is missing though). Mimic the implemented solution for the bitstream. Heavy testing is required to verify that embargo is also respected once the items are archived. NEEDS DISCUSSION. UNCERTAIN | 20 | 1. needs ticket(s) | May be combined with "Make an Item Private". "Requires senior developer - Write a custom section component to render the Access section - Write a service to parse the access section data, and send patches back to the server" | 30 | 1. needs ticket(s) | |||||||||||||||||
49 | Submission | Make an Item private | REST functionality exists | 0 | 6. draft implementation | Need option to make Item Private during submission. Depends on Embargo Item Metadata (form Submission UI Only) - Add the private item checkobx to the access section component - Ensure the service can parse the response, and send patches concering the private item status | 6 | 1. needs ticket(s) | |||||||||||||||||
50 | Submission | Type-bind submission | Some metadata should be included only for specific value of dc.type https://wiki.duraspace.org/display/DSDOC6x/Submission+User+Interface#SubmissionUserInterface-ItemtypeBasedMetadataCollection | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
51 | Submission | Controlled-vocabulary | Some institutions use hierarchical vocabulary https://wiki.duraspace.org/display/DSDOC6x/Submission+User+Interface#SubmissionUserInterface-ConfiguringControlledVocabularies | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
52 | Submission | Sherpa-Romeo Integration | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | |||||||||||||||||||
53 | Submission | Creative Commons | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | |||||||||||||||||||
54 | Submission | ORCID Lookup | It should work unchanged as the authority framework is supported but I guess it deserves a row for importance | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
55 | Workflow | Support for General Configurable Workflow steps. | Need to be able to retrieve all steps and actions via REST API. Required for all other sample steps (see "Select Single Reviewer", and "Score review workflow" below). NEEDS REST Contract. General Configurable Workflow, retrieiving steps & actions. See https://jira.duraspace.org/browse/DS-4180 | 12 | 1. needs ticket(s) | Requires rendering workflow actions dynamically | TBD | 1. needs ticket(s) | |||||||||||||||||
56 | Workflow | Additional configurable workflow steps: "Select Single Reviewer Workflow" | https://wiki.duraspace.org/display/DSDOC6x/Configurable+Workflow#ConfigurableWorkflow-Additionalworkflowsteps/actionsandfeatures Needs developer familiar with this feature (Atmire). LOWER PRIORITY, NOT WIDELY USED. Create the backend to store the information Creating a REST API to identify which identifies the options per step should be part of https://jira.duraspace.org/browse/DS-4279 | 9 | 1. needs ticket(s) | - AssignStep - Add a component to select a reviewer to assign - Add methods to a submission service to search for applicable reviewers, and to assign a reviewer to a workflowitem - ReviewStep - Everything should already be in place on the UI side Assumes render workflow action dynamically is completed (see above). UNCERTAIN | 18 | 1. needs ticket(s) | |||||||||||||||||
57 | Workflow | Additional configurable workflow steps: "Score review workfow" | Needs developer familiar with this feature (Atmire). LOWER PRIORITY, NOT WIDELY USED. Create the backend to store the information Creating a REST API to identify which identifies the options per step should be part of https://jira.duraspace.org/browse/DS-4279 | 14 | 1. needs ticket(s) | - ScoreReviewStep - Add a component to enter the score. - Enforce that the score is a valid percentage - Add buttons to submit the score, or leave the step - Add a method to the appropriate submission service to send the score to the REST API Assumes render workflow action dynamically is completed (see above). UNCERTAIN | 9 | 1. needs ticket(s) | |||||||||||||||||
58 | Workflow | Administer Workflow (Abort WorkflowItem, Delete WorkflowItem, Send back to Submitter) | Abort WorflowItem already exists (which sends item back to Submitter). Can already findAll on this endpoint, but it's very basic (so no Search configuration exists for WorkflowItems). Delete Item may be low priority? | TBD | 1. needs ticket(s) | - Add buttons to abort, delete and send back to the workflowitem actions component - Implement the methods in the appropriate submission service to send those actions to the rest api Requires new search configuration. More of this is on the REST side though, but requires configuration in the Angular UI (as this is not dynamic). | 20 | 1. needs ticket(s) | |||||||||||||||||
59 | Batch Export | Export Community (to ZIP) | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
60 | Batch Export | Export Community Metadata (to CSV) | See https://jira.duraspace.org/browse/DS-4060 Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
61 | Batch Export | Export Collection (to ZIP) | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
62 | Batch Export | Export Collection Metadata (to CSV) | See https://jira.duraspace.org/browse/DS-4060 Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
63 | Versioning | Create new Item Version | https://wiki.duraspace.org/display/DSDOC6x/Item+Level+Versioning In JSPUI, possible for submitters to version own items. In XMLUI, only Admins or Com/Col Admins can version. | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
64 | Batch Export | Export Item (to ZIP) | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
65 | Batch Export | Export Item Metadata (to CSV) | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | On hold, likely to be redesigned using the scripts and processes endpoint | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
66 | Edit | Embargo an archived Item | In DSpace 6.x, this was done via editing Resource Policies directly (see "Edit Item - Manage Resource Policies / Roles") | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
67 | Edit | Create/Manage a Collection Item Template | Depends on an Edit Collection endpoint (already exists). POST to /api/core/collections/:uuid/templateItem to create an empty item, DELETE to remove the template. PUT is not required | 12 | 1. needs ticket(s) | This has been started within Atmire already and is almost completed. | 14 | 1. needs ticket(s) | |||||||||||||||||
68 | End User | Request a Copy | https://wiki.duraspace.org/display/DSDOC6x/Request+a+Copy See https://jira.duraspace.org/browse/DS-3952 Work begun in https://github.com/DSpace/DSpace/pull/2129 (but needs significant work) | 20 | 3. ready to be worked on | - Item page - Indicate when the user doesn't have access to one or more files - Add a link or button to request a copy - Requester Form - Create the requester form - Create a service to send the request data to the REST API - Submitter Grant Form - Add a method to the data service to validate the submitter token with the REST API - Create the submitter form - Add a method to the data service to send the the submitter data to the REST API - Submitter Change Permissions form - Create the change permissions form, show it after access is granted in the previous form - Add a method to the data service to send the grant permission request to the REST API | 22 | 3. ready to be worked on | |||||||||||||||||
69 | Edit | Edit Item (Submission Style) - NEW FEATURE FROM 4Science | This is a new feature where users can edit an Item using a submission-like form (instead of the old v6.x edit metadata screens, etc) Feature existed in the OR2018 demo code, but was never extracted into a PR. Uncertain how difficult this effort would be. | TBD | 2. backlog (temporarily on hold) | TBD | 2. backlog (temporarily on hold) | ||||||||||||||||||
70 | Edit | Edit Community - Assign Roles/Groups | (Similar to Item Templates) Endpoint should only initialize the empty group (for the community administrators) and the ability to remove such group. Later group changes can use the Manage Groups endpoint. Additional Roles could be defined by the configurable workflow but they are out of scope of this task | 8 | 1. needs ticket(s) | This task depends on Manage Groups - Add the "assign roles" tab to the edit community page - Add the ability to retrieve or parse (e.g. from the _links section on an existing endpoint) the possible roles for a community or collection to the ComColDataService - Create a component to represent a role in an Com/Col roles tab - Add a method to the groups service to create a group for a role + community or collection combination (the UI shouldn't have to know how to name that group) - Link to the edit group page for a group if one exists | 18 | 1. needs ticket(s) | |||||||||||||||||
71 | Edit | Edit Collection - Assign Roles/Groups | This is similar to the previous task. We can save time if the task is performed by the same developer than the previous one. The estimation is only related to the "hardcoded" groups: Collection Administrator, Submitters, Default Item Read. Needs to *exclude* Workflow specific groups. | 15 | 1. needs ticket(s) | This task depends on Edit Community - Assign Roles/Groups (above). Both tasks could be done by same developer at same time. - Add the "assign roles" tab to the edit collection page - Use the roles component created for r21 for each of the available roles | 2 | 1. needs ticket(s) | |||||||||||||||||
72 | Edit | Edit Community - Upload Logo | In progress already: https://github.com/DSpace/DSpace/pull/2562 | 9 | 5. awaiting review | - Render the logo if it exists on the edit community page - Add a way to remove it - Add a dropzone similar to the submission for file uploads to upload a new logo - Add methods to the ComColDataService to upload and delete the logo Estimate assumes we can reuse the submission uploader | 14 | 1. needs ticket(s) | |||||||||||||||||
73 | Edit | Edit Collection - Upload Logo | In progress already: https://github.com/DSpace/DSpace/pull/2562 | 6 | 5. awaiting review | This task depends on Edit Community - Upload Logo (previous task). Should be done by same developer - Reuse the components created for that feature on the edit collection page | 2 | 1. needs ticket(s) | |||||||||||||||||
74 | Edit | Edit Collection - Harvesting Settings | https://github.com/DSpace/DSpace/pull/2491 | 2 | 1. needs ticket(s) | Atmire is already working on the angular UI as well. Done: - The content source tab on the edit collection page has been added an allows you to configure the params and store them to the server Still to do: - Start harvesting and show the status Specs: - Add UI elements to start a harvest and show the status - Start jobs using the scripts&processes endpoint - Get the status from the collection /harvest endpoint | 9 | 1. needs ticket(s) | |||||||||||||||||
75 | Edit | Edit Item - Manage Bitstreams | https://github.com/DSpace/Rest7Contract/pull/71 | 11 | 1. needs ticket(s) | Atmire is already working on this. Done: - The edit bitstreams tab on the edit item page, with an overview of the available bitstreams - Adding new bitstreams - Editing existing bitstreams Still to do, everything involving Bundles: - Reordering bitstreams - Grouping the bitstreams by bundle in the edit bitstreams tab - Support for uploading bitstreams to something other than the ORIGINAL bundle This work is waiting on REST support for Bundles | 12 | 1. needs ticket(s) | |||||||||||||||||
76 | Edit | Edit Item - Manage Resource Policies / Roles | We should implements the CRUD operation over the resourcepolicies endpoint without having dedicated endpoint for the "item's resourcepolicies". DELETE POST PATCH verbs are required. Bulks changes are out-of-scope for this task. Security needs to be implemented. NOT A TRIVIAL ENDPOINT. Early contract: https://github.com/DSpace/Rest7Contract/pull/87 | 30 | 1. needs ticket(s) | - Add a link to the item policies page to the item status tab - Create the policies page component - Show the current policies for the Item, and each bundle and bitstream within the item - Add the ability to edit or remove each exiting policy - When showing groups, add a link to their edit group page - Add the ability to add a new policy for the item and each bundle and bitstream within the item - Add methods to the ItemDataService, or a dedicated PolicyService to - retrieve all policies for an item grouped by bundle and bitstream - support CRUD for policies → you should be able to reuse DataService code for this | 24 | 1. needs ticket(s) | |||||||||||||||||
77 | Versioning | Create a new item version as submitter | This feature only existed in JSPUI | TBD | 1. needs ticket(s) | TBD | |||||||||||||||||||
78 | Versioning | List version history | TBD | 1. needs ticket(s) | TBD | ||||||||||||||||||||
79 | Versioning | When viewing an old version, provide a notice regarding the availability of the new version | TBD | 1. needs ticket(s) | TBD | ||||||||||||||||||||
80 | Admin | Bulk Access Control Management (Wildcard / Advanced Policy Manager) | This is the Wildcard/Advanced Item Policy tool in v6.x | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
81 | Admin | Manage EPeople | DS-3735, DS-4021 | 0 | 6. draft implementation | - Create an EPerson Management page - It should contain a paginated search of the EPersons in the system - Render the results like the edit item bitstreams or metadata page: - show ID, Name and Email columns for each EPerson - and add an actions column at the end containing edit and delete buttons - Create a component to add/edit EPersons - show fields for email, first name, last name, telephone, can log in and require certificate - when in edit mode, - show buttons to reset password, delete the eperson and to log in as the eperson (when permitted) - List the groups the EPerson is a part of with links to the edit page for each group - Create an EPersonDataService based on DataService with CRUD methods for epersons. - It will need a search method that isn't part of the default set - Hook up the Manage People link in the admin menu | 23 | 1. needs ticket(s) | |||||||||||||||||
82 | Admin | Manage Groups | Can create groups already (DS-4023). We need to implement add/remove eperson and groups from Group. The contract is specified in the DS-4026. A senior developer is required to implement it according to the suggestion. Early work at https://github.com/DSpace/Rest7Contract/pull/41 | 22 | 3. ready to be worked on | - Create an Group Management page - It should contain a paginated search of the Groups in the system - Render the results like the edit item bitstreams or metadata page: - show ID, Name, Members and Community/collection columns for each Group - and add an actions column at the end containing edit and delete buttons - Create a component to add/edit Group - show a field for the group name, and a search box to allow you to search for either groups or epersons - Show the results in a paginated table, columns ID, name email and actions, - If they're not in the group, show the add action, if they're part of the group show a remove action - when in edit mode, show a paginated list of the members in the group - Don't use a table like dspace 6, use a list instead, because it can contain both groups and eperons - Add a remove action after each one - Create an GroupDataService based on DataService with CRUD methods for groups. - It will need a search method that isn't part of the default set however this is very similar to the EpersonDataService, so it can probably be reused between the two - Hook up the Manage groups link in the admin menu Note The UI for editing a group could use some thought. It's very clunky | 28 | 1. needs ticket(s) | |||||||||||||||||
83 | Admin | Find Item by Internal Item ID (UUID) or Handle | Exists as "/api/pid/find" | 0 | 7. completed | - Create an administrative version of the Search page on an alternate URL - The idea is that it would be configured on the backend with a facet for withdrawn or private - Modify the search result components for each DSO to show a label if an item is private or withdrawn. - Refactor the search service to be able to reuse it for this administrative search - Hook up the admin menu links This task is combined with the next 2 tasks (Browse Withdrawn and Browse Private). Same developer | 20 | 1. needs ticket(s) | |||||||||||||||||
84 | Admin | Withdrawn Items (browse by Title) | https://jira.duraspace.org/browse/DS-3906 Also requires additional ITs. This should be implemented at same time as Browse Private Items | 26 | 3. ready to be worked on | Task should be combined with "Find Item by Internal Item ID" task . This should be a facet of that same Admin search feature (which is why this is a zero estimate) | 0 | 1. needs ticket(s) | |||||||||||||||||
85 | Admin | Private Items (browse by Title) | https://jira.duraspace.org/browse/DS-3906 Also requires additional ITs. This should be implemented as part of Browse Withdrawn Items (which is why this task has a zero estimate) | 0 | 3. ready to be worked on | Task should be combined with "Find Item by Internal Item ID" task . This should be a facet of that same Admin search feature (which is why this is a zero estimate) | 0 | 1. needs ticket(s) | |||||||||||||||||
86 | Admin | Control Panel | This is an XMLUI only feature in 6.x. REQUIRES DICUSSION | TBD | 1. needs ticket(s) | This is an XMLUI only feature in 6.x. Unclear what is possible in Angular. REQUIRES DISCUSSION | TBD | 1. needs ticket(s) | |||||||||||||||||
87 | Batch Import | Import Metadata CSV (no Preview of Changes Feature) | https://jira.duraspace.org/browse/DS-4060 (needed for Entities). Dependent on Scripts & Processes The implementation of this script will require: * A migration of 2 command line scripts * Support for non-admins to perform some scripts | 7 | 3. ready to be worked on | Initial version (based on basic drag & drop, and then a status of success or failure). Does NOT include Preview of changes, as that was split out into a separate task by the REST API team. | 8 | 1. needs ticket(s) | |||||||||||||||||
88 | Batch Import | Import Metadata CSV (Enhanced, with Preview of Changes, as in v6.x) | Adds the capability to preview the changes and exports search result, which will require a dedicated endpoint (beyond the generic "scripts & processes" endpoint) An endpoint is needed /utilities/bulkedits where POST is used to create a new bulkedit preview. The final import can be done via the scripts endpoint supplying the preview uuid (that can be used as name of the temporary file). DELETE will cancel the bulkedits removing the files, otherwise a cleaning script can be used to remove file older than a defined period. The dspace-api should be revisited to allow pagination of the changes in the preview but this is postponed to a future improvement. | 26 | 1. needs ticket(s) | Note this assumes the export CSV functionality is part of a different task. It also assumes the backend has separate independent endpoints for the preview and the actual import - Create an Import metadata page - Reuse the dropzone from the submission to upload the file - Show the pending changes on the same page after the upload succeeds - Also reuse that page for the overview after the import is executed - Create a service to communicate with the import csv endpoint. With methods to: - POST a CSV file to a preview endpoint, and get a response of what the changes would be - POST a CSV file to an import endpoint and get a response of what was executed. | 14 | 1. needs ticket(s) | |||||||||||||||||
89 | Batch Import | Batch Import (from ZIP) | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | TBD | 2. backlog (temporarily on hold) | ||||||||||||||||||
90 | Admin | Curation Tasks | Depends on "Scripts & Processes" endpoint | TBD | 2. backlog (temporarily on hold) | https://github.com/DSpace/dspace-angular/issues/285 | TBD | 2. backlog (temporarily on hold) | |||||||||||||||||
91 | Admin | Supervision Orders (JSPUI Only) | Needs DCAT feedback? Unclear if this is used much. See JSPUI: http://demo.dspace.org/jspui/dspace-admin/supervise | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
92 | Admin | Edit Homepage News from Admin UI (JSPUI Only) | Early work: https://github.com/DSpace/Rest7Contract/pull/45 See JSPUI: http://demo.dspace.org/jspui/dspace-admin/news-edit | TBD | 4. in progress | TBD | 1. needs ticket(s) | ||||||||||||||||||
93 | Admin | Edit Default Deposit License from Admin UI (JSPUI Only) | See JSPUI: http://demo.dspace.org/jspui/dspace-admin/license-edit | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
94 | Admin | Login as EPerson | Use case is similar to "Supervision Orders". Allows helping someone or debugging issues by seeing what they see. See XMLUI "Edit EPerson" page or the JSPUI e-people administrative page. There's a button called "Login as E-Person". https://wiki.duraspace.org/display/DSDOC6x/Configuration+Reference#ConfigurationReference-Loginasfeature See https://jira.duraspace.org/browse/DS-3934 | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
95 | GDPR | Delete EPerson | https://jira.duraspace.org/browse/DS-4036 REQUIRED FOR GDPR COMPLIANCE Add test to verify that inprogress submission are deleted as well, including pending workflow tasks. Add test to verify that the EPerson is removed from Groups without touching other members. Add test to include item without submitter in Search and Browse endpoint. Add test to check edit of item with null submitter. Add tests related to verify that subscriptions and request-a-copy about such eperson are deleted as well. Add test to include submitter null item in the versioning items endpoint (or create a task for future check) Add a configuration parameter to limit the DELETE operation to only administrator and implement proper security | 29 | 3. ready to be worked on | This is a subtask of "Manage EPeople" task (for Angular UI) | 0 | 1. needs ticket(s) | |||||||||||||||||
96 | Admin | Scripts and Processes (Lots of features dependent on this one) | New endpoint which allows key commandline scripts (Curation Tasks, export/import scripts) to be kicked off via a single REST API endpoint. Discussed in detail on Sept 22, 2019 See https://github.com/DSpace/Rest7Contract/pull/17 and https://github.com/DSpace/DSpace/pull/2529 | TBD | 4. in progress | 0 | (not applicable) | ||||||||||||||||||
97 | Statisics | Google Analytics support | https://jira.duraspace.org/browse/DS-4059 (Provide Analytics Key via REST). Create an endpoint /config/paramters/:param that provide GET access to the configuration. Add a service configured via spring mantaining a list of protected key that can be only exposed to administrator. The estimation is only related to the implementation of a direct access to a specific parameters. No listing capabilities seems needed for now. Investigation is needed to found the best way to express the parameter if it is "single value" or an "array" | 17 | 3. ready to be worked on | Basic support already exists. Enhancements already up for review in https://github.com/DSpace/dspace-angular/pull/495 | 0 | 5. awaiting review | |||||||||||||||||
98 | Statistics | DSpace (Solr) Statistics - Tracking Events | See https://jira.duraspace.org/browse/DS-3574. REST Contract for tracking events for statistics exists at https://github.com/DSpace/Rest7Contract/pull/63 | TBD | 3. ready to be worked on | TBD | 1. needs ticket(s) | ||||||||||||||||||
99 | Statistics | DSpace (Solr) Statistics - Sitewide Usage Reports (same as v6.x) | Reports include: top 10 Items in total visits | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||
100 | Statistics | DSpace (Solr) Statistics - Community/Collection Usage Reports (same as v6.x) | Reports include: Total Community/Collection Visits (overall, per month over last 6 months). Top Country Views. Top City Views | TBD | 1. needs ticket(s) | TBD | 1. needs ticket(s) | ||||||||||||||||||