Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore Primary Bitstream as a capability of DSpace 7 #3349

Closed
hardyoyo opened this issue Jul 28, 2021 · 9 comments · Fixed by #8876
Closed

Restore Primary Bitstream as a capability of DSpace 7 #3349

hardyoyo opened this issue Jul 28, 2021 · 9 comments · Fixed by #8876
Assignees
Labels
claimed: Atmire Atmire team is working on this issue & will contribute back e/0 Estimate in hours high priority needs funding Ticket will likely require funded development to implement new feature
Milestone

Comments

@hardyoyo
Copy link
Member

hardyoyo commented Jul 28, 2021

Is your feature request related to a problem? Please describe.
Prior versions of DSpace had a field in the Bundle table [1] which provided a link to a bitstream, called 'primary_bitstream_id'[1] This was used to determine what thumbnail to show for a specific item that had multiple bitstreams attached. This would also help for instances of scholarly publications, where you would have the "primary" bitstream as the PDF of the article, and then any supporting bitstreams (images, other media files, software, a data set, etc.)

Describe the solution you'd like
There needs to be a way to indicate whether a bitstream is a “primary bitstream” for an item. This should be part of the ingest process, and should be utilized in thumbnail selection for items. This metadata should also be accessible to item templates, so that a designated primary bitstream can be displayed differently on an item page, in order to give it prominence, and to otherwise fit an institution’s use case and site designs. The text extracted from a primary bitstream should also be given a higher relevance ranking in the fulltext search index.

UPDATE from DevMtg on April 7, 2022: All the functionality of "primary bitstreams" still exists in the codebase, but the REST endpoints are missing. We discussed the solution is likely two REST endpoints:

Describe alternatives or workarounds you've considered
Use an earlier version of DSpace, or reorder bitstreams so that the "primary" is listed first (as first bitstream is considered the primary one when no primary is selected)

Additional context
Add any other context or screenshots about the feature request here.

@hardyoyo hardyoyo added new feature needs triage New issue needs triage and/or scheduling labels Jul 28, 2021
@mwoodiupui
Copy link
Member

This would be an opportunity to re-think the concept. For one thing, if we consider "primary Bitstream" to be a property of an Item, then what is it doing in Bundle? Right now each Bundle has a primary Bitstream. Why?

While we're at it, we should consider the effort involved in matching derivative Bitstreams to their sources. Does a Bitstream have metadata: has-{thumbnail | text | etc.} [derived Bitstream's ID]? Should it?

@hardyoyo
Copy link
Member Author

hardyoyo commented Aug 4, 2021

According to the REST Contract the bundle endpoint still has a notion of "primary bitstream". If this is correct, I'd like to see DSpace-Angular provide a UI for it (say a checkbox for an item's bitstreams). FYI, we're working on drafting at least one formal use case for this feature request.

@tdonohue
Copy link
Member

tdonohue commented Aug 5, 2021

As there's already a lot on our 7.1 board, and this has a basic "workaround" (reorder the bitstreams so the first one is most important), I'm going to move this to our 7.2 board for now. That said, if someone has an opportunity to work on this earlier, any community contributions are welcome in 7.1. It also might be reprioritized as further use cases come in.

@tdonohue tdonohue added Estimate TBD Needs to have an estimate added and removed needs triage New issue needs triage and/or scheduling labels Aug 5, 2021
@tdonohue tdonohue added this to To Do in DSpace 7.x Tier 2: Medium High Priority via automation Aug 5, 2021
@tdonohue tdonohue added the help wanted Needs a volunteer to claim to move forward label Sep 3, 2021
@mwoodiupui
Copy link
Member

Further to re-thinking: why is it possible for an item to not have a primary bitstream?

For that matter, precisely what does "primary" mean to DSpace?

@hardyoyo
Copy link
Member Author

hardyoyo commented Mar 1, 2023

I can tell you what I think it ought to mean to DSpace: a "primary" bitstream should be the bitstream used for generating a thumbnail for the item. It should also be the first listed bitstream in a list of bitstreams associated with an item, in the UI.

@tdonohue
Copy link
Member

tdonohue commented Mar 1, 2023

Just wanted to note here... that the meaning of "primary" bitstream has become confusing to me as of late. It used to be exactly what @hardyoyo states. However, now that Bitstreams are easily reorderable (via drag & drop), the first listed bitstream is simply the one used for the Item thumbnail.

So, in a way, the use case @hardyoyo notes is already in DSpace 7. Just drag & drop reorder your "primary" bitstream to be first in the list. That will be used as the Item thumbnail.

Hence, I'm also questioning the true meaning / use case of "primary" bitstream. I think it was initially created at a time when bitstream reordering was difficult. (If I'm wrong though, please correct me) But, does it still have a use case when bitstream reordering is now easy to achieve either in the Submission UI or Edit Item pages?

@hardyoyo
Copy link
Member Author

hardyoyo commented Mar 1, 2023

I would say that ordering of bitstreams would be "implicit" while a toggle would be "explicit". Though, redesigning the submission form, with a big arrow pointing to the top of the list of bitstreams with "primary bitstream" on it... might make this explicit enough.

@tdonohue tdonohue added the needs funding Ticket will likely require funded development to implement label Mar 9, 2023
@tdonohue
Copy link
Member

Per today's meeting, assigning to @artlowel & @benbosman / Atmire for 7.6. Thanks!

Per Steering decision on March 22, this work is funded development for 7.6.

Steering approved this & DSpace/dspace-angular#1578 based on a combined estimate of about 60hrs effort. Therefore, I'm adding a zero hour estimate to this ticket as it's included in the 60hr estimate attached to DSpace/dspace-angular#1578

@tdonohue tdonohue added e/0 Estimate in hours claimed: Atmire Atmire team is working on this issue & will contribute back and removed Estimate TBD Needs to have an estimate added help wanted Needs a volunteer to claim to move forward labels Mar 23, 2023
@tdonohue tdonohue added this to the 7.6 milestone Jun 22, 2023
@Rajamuthukrishna
Copy link

Hello Team,

I need to find the items which is not available in thumbnails, kindly share any API is available for this, otherwise share which table is used for thumbnail Id is stored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
claimed: Atmire Atmire team is working on this issue & will contribute back e/0 Estimate in hours high priority needs funding Ticket will likely require funded development to implement new feature
Projects
No open projects
Archived in project
6 participants