Status: Accepted
Owner: [email protected]
Labels: Type-Enhancement Priority-High Milestone-Release-1.2
Component-Import-Export Component-EAD
New issue 1924 by [email protected]: Allow update of existing
descriptions via EAD
http://code.google.com/p/qubit-toolkit/issues/detail?id=1924
On 7-Jan-11, at 12:30 PM, Peter Van Garderen wrote:
The simplest and most realistic technique will be to (1) simply import the
updated records and delete the existing records (as per Chris's
description). The ideal scenario would be to (2) have some type of
versioning where Qubit recognizes that the import is a match to an existing
record and gives the user the option to (a) delete and replace the target
record or (b) merge any changes to the target record. Technique (1) will
also have an affect on permalinks. Will deleting the old records first
(i.e. before the import) free up the permalink for the imported updated
records? If using technique (1) is there a way to avoid losing the
permalink?
To enable this feature for a portal scenario like MemoryBC, we will have to
think about how to apply ACL rules so that the administrator can grant
permission to individual users to upload EAD and then ensure that they are
only able to upload EADs for their repository only. Presumably the standard
publication workflow would apply wherein the EAD uploads would be
assigned 'draft' status and approved by the administrator for 'publication'
status.
--
You received this message because you are subscribed to the Google Groups "Qubit
Toolkit Issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/qubit-issues?hl=en.
