imiro / dspace Goto Github PK

Currently journal title is saved to dc.publisher qualifier. It might be a good idea to move them all to dc.publisher.jtitle or dc.publisher.journaltitle or something similar, as dc.publisher may contain different, more related value such as "Lippincott William & Wilkins" or "Elsevier"

This is important for compatibility before integrating with MRU's information system.

While on adminsitrators' view, header logo image will overflow the bottom header line.

On Edit Collections view, the right sidebar items kind of overlap each other

Currently, user submission workflow only allows an item to be assigned to one collection, i.e. its parent collection.

On the contrary, an administrator is able to bulk upload an item and assign it to multiple collections at once. Bring this capability on user submission.

Note: workflow curator may or may not approve the collection inputted by the user, or just arbitrarily alternate to which collection should it be assigned based on his/her judgment.

If bitstream is uploaded; will authority service works as it should be?

Sipeg/sinta has this capability to export all the contents displayed into a print-friendly page, so that it can be printed as CV of some sort.

Which metadata should be exported?
Maybe in citation-like format, such as vancouver?

Currently, all users logged in via SSO is assigned the following: (first name="University", last name="User").

This can be further improved either by:

• Redirecting user to edit profile page on first login
• Get the data (XML parsing from CAS/SSO) automatically

Happening on the live version now (06/2020), the sort by date does not behave as it is expected to be.
It now sorts the publications by date on "batches", so results 1-10 are correctly sorted (2019/07 -> 2018/01), but then items 11-25 shows different date format and it broke (2020-May -> 2018-Jul or something).

Explore.

There should be at least one user/user group assigned with WORKFLOW_STEP_1 permission to all collections, so that logged in user (via SSO-UI) won't be able to publish item arbitrarily without further curation process.

During user item submission, if the item type chosen on the first page is either published articles or book, skip the entire file upload process.

Curently, there is no visual cue on

1. Whether a collection is already selected
2. If yes, WHERE is the currently selected collection

Second, the order in which the collection appeared is currently in arbitrary order.
We can improve it by alphabetically sorting them.

This is a different problem and probably should have been issued in different thread

Analyze the tag on Pubmed's XML and automatically generate suggestion and write its handle to a certain csv column.