Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

  • Revisiting "Collection dropdown in submission”  (Estimation REST 1 day including small contract change / Angular 1 day): the existence of the “Collection dropdown”  within the submission can be associated with the configuration of the "collection" step. If the collection step is not defined in the submission definition the “Collection dropdown” will be not showed

        <submission-process name="traditional">

            <step id="collection"/>

            <!--Step will be to Describe the item. -->

            <step id="traditionalpageone"/>

            <step id="traditionalpagetwo"/>

            <!--Step will be to Upload the item -->

            <step id="upload"/>

            <!-- <step id="upload-with-embargo"/> -->

            <!-- <step id="detect-duplicate"/> -->

            <!--Step will be to Sign off on the License -->

            <step id="license"/>

            <!-- <step id="creative-commons"/> -->

            <!-- <step id="verify"/> -->

        </submission-process>

This will made “Collection dropdown” configurable giving the opportunity to the user to completely disable this feature if not liked.

Template item: we suggest to add a flag in the collection object returned by REST to indicate that such collection includes a template item. The flag is needed to avoid permission issue in reading the actual item template that is not really needed to be known by the client (for the submitter). If the user try to change the collection toward a collection that has a template item the “Collection dropdown” show a warning message asking confirmation to the user. The user will be allowed to decide if they want to apply the item template or not or cancel the collection change.

  • performance issues: https://github.com/DSpace/dspace-angular/issues/487 (Estimation Angular 2 days) the dropdown collection component had better be refactored by using pagination for the collection list and by retrieving community by the new `parentCommunity` collection’s link. The lookup function needs to be revisited if the collection list is paginating
  • Changing Collection would result in a different form definition (Estimation Angular 2h): similar to the scenario of the template item a warning can be shown and if the user need to explicitly confirm the switch. Estimation no change required on the REST side
  • Further considerations Starting a new submission from the “new item” sidebar’s link is not always usable for a not admin user. We hear from our customers that many researchers use the repository unfrequently and they don’t know and don’t remember about the repository structure, for them it is pointless to make a search because essentially they don’t know the available options. They expect to have list / tree to browse for them a lookup is not the best approach to use. Moreover it does not consider the user's permissions on collections. Considering this, a new feature which allows to select the start collection could be implemented in the mydspace page. It could be realized starting from community-list tree considering authorizations issues.
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.