References to bitstreams not from the 'ORIGINAL' bundle are shown in harvested
items
Key: DS-1055
URL: https://jira.duraspace.org/browse/DS-1055
Project: DSpace
[
https://jira.duraspace.org/browse/DS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22797#comment-22797
]
Àlex Magaz Graça commented on DS-1050:
--
Ok, I've opened a new bug report here:
[
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22798#comment-22798
]
Robin Taylor commented on DS-768:
-
dspace-xmlui-wing/pom.xml updated to pick up version 1.0.3 of
[
https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Taylor resolved DS-599.
-
Documentation Status: Complete or Committed (was: Needed)
Resolution: Fixed
SOLR statistics
[
https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22799#comment-22799
]
Robin Taylor commented on DS-599:
-
The documentation looks great !
Cheers, Robin.
[
https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22800#comment-22800
]
Kevin Van de Velde commented on DS-599:
---
Thanks for checking up on it Robin. Could you perhaps
[
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22801#comment-22801
]
Tim Donohue commented on DS-587:
Mark,
I don't think we should be consolidating DS-135 into this
[
https://jira.duraspace.org/browse/DS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-135:
---
Attachment: Clean_Tombstone_Via_Restricted_Item.patch
Attaching Mark Diggory's DS-135 patch to this issue
[
https://jira.duraspace.org/browse/DS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-135:
---
Attachment: tombstone-screen.jpg
Mark,
I'm slightly confused as to the usage of the new tombstone page (for others
[
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22804#comment-22804
]
Mark Diggory commented on DS-587:
-
Ok, let's move my patch there and solve the bug issue only.
[
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-587:
---
Attachment: (was: Clean_Tombstone_Via_Restricted_Item.patch)
add the capability to indicate a withdraw
[
https://jira.duraspace.org/browse/DS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22805#comment-22805
]
Tim Donohue commented on DS-587:
Done. Your 'Clean_Tombstone_Via_Restricted_Item.patch' tombstone patch
[
https://jira.duraspace.org/browse/DS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22806#comment-22806
]
Mark Diggory commented on DS-135:
-
1. Your right, that was supposed to be in the patch.
2. Was to
[
https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22807#comment-22807
]
Peter Dietz commented on DS-599:
Hi Kevin,
I've been getting lots of java out of memory error's trying
[
https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=22808#comment-22808
]
Peter Dietz commented on DS-599:
I've changed to using getResponseBodyAsStream, and there is some
Hi, a recent thread on dspace_tech [1] got me thinking about my previous
experiences with caching, in other web development environments. In
particular, a few years back, I did a lot of development using a PHP-based
framework called ezPublish, and it had a caching scheme that could, on
occasion,
Hi Hardy,
I've used the clearcache functionality on our production site, and it is
useful for performing manually, when your site is just stuck. I think it
would be best to hide the url in a location that public users can't access
site/protected/clearcache, just because they shouldn't have access
IMO I think that while I originally proposed this solution, it may not
completely undo our current problems. the following changes introduced a
behavior into the XMLUI that no longer allows the page to state it has
changed because the following selector preempts this process and forces
response
18 matches
Mail list logo