[
http://jira.dspace.org/jira/browse/DS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10479#action_10479
]
Sands Fish commented on DS-192:
-------------------------------
So, my understanding is that the intended use of the bitstream sequence_id was
simply a unique identifier. If, by "reorder", you mean change, will this not
potentially break bistream IDs? If so, it seems we'd need another mechanism
for controlling display order.
> Bitstreams should be returned ordered
> -------------------------------------
>
> Key: DS-192
> URL: http://jira.dspace.org/jira/browse/DS-192
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: DSpace API
> Affects Versions: 1.5.0, 1.5.1, 1.5.2
> Reporter: Flávio Botelho
> Priority: Minor
> Attachments: ordering_bitstreams.patch
>
>
> There exists a sequence_id for bitstreams, but it is not being used to return
> the bitstreams ordered.
> Important for items with lots of bitstreams, usually you want ensure some
> order to them.
> The patch goes with DESC ordering because it seemed to fit more what ordering
> would usually happen in practice, but maybe should be changed to ASC;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
