[
http://jira.dspace.org/jira/browse/DS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Shepherd updated DS-240:
----------------------------
Attachment: DS-240_DSpaceValidity_item.patch
This patch adds the owning collection ID and last modified date to the item's
validity key, so that item moves, maps and anything else that alters an item
without changing metadata will not result in old cached objects being served in
ArtifactBrowser, etc.
Including last modified date will ensure that most of these sorts of operations
result in the cache being updated, but in the event that an administrator
performs manual SQL updates on owning_collection (not unheard of) without
updating last_modified, the cache will still be updated.
It may be worth thinking about other values in the item table that could
potentially change as new features are added.
> Item validityKey not complete
> -----------------------------
>
> Key: DS-240
> URL: http://jira.dspace.org/jira/browse/DS-240
> Project: DSpace 1.x
> Issue Type: Bug
> Components: XMLUI
> Affects Versions: 1.5.2
> Reporter: Stuart Lewis
> Fix For: 1.6.0
>
> Attachments: DS-240_DSpaceValidity_item.patch
>
>
> An item's validityKey does not contain information about when it was last
> updated, or what its owning collection is. Therefore when an item is moved
> between collections, the pipeline cache is not updated.
--
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
------------------------------------------------------------------------------
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
