Title: Message Title
|
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned
|
|
Created:
|
19/Jun/14 5:16 PM
|
|
Priority:
|
![Trivial]() Trivial
|
|
Reporter:
|
Alex
|
|
Original Estimate:
|
6 hours
|
|
Remaining Estimate:
|
6 hours
|
|
I think it will be good for dspace to remember each handle and bitsitream order even after it will be deleted. For example, we have a good link - http://elar.urfu.ru/bitstream/10995/4565/2/urfu0995s.pdf but it is a 2nd version of file. 1st was here - http://elar.urfu.ru/bitstream/10995/4565/1/urfu0995s.pdf and user usually get a 404 error without additional information, but I make a 302 redirect (I have about 5 000 of 302 redirects now). System can show the message, for example “file was deleted or modified, please see the item handle page (link)”.
I have only ugly method - I think it will be good to patch 404 page
This is a right link - http://elar.urfu.ru/bitstream/10995/4565/2/urfu0995s.pdf
This is a wrong link - http://elar.urfu.ru/bitstream/10995/4565/3/urfu0995s.pdf
We have a link "страницей описания" on it. It is a very simple _javascript_ link with one regexp. If we have a broken bitstream, we will get the link to the ITEM, if we have a broken ITEM link, we get the link to community list.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
