Comment #1 on issue 1924 by [email protected]: Allow update of existing
descriptions via EAD
http://code.google.com/p/qubit-toolkit/issues/detail?id=1924
On Thu, 2011-01-20 at 14:33 -0800, David Juhasz wrote:
The only difficulty I can see for allowing the update of existing
descriptions is in choosing how to match an existing description to the
new "incoming" version. I would think the title of the Fonds should be a
unique, static key we could use for matching existing descriptions. Once
we have a key to match the new version of a description to the old one,
doing the update should be straight-forward. If the Fonds title has not
changed the permalink generated by the system should be identical. I
should note that this is assuming a delete of the old description and
insert of the updated description - not some sort of incremental update.
Peter, are you talking about allowing end-users to do bulk EAD uploads?
I think there are some very good reasons to *only* allow the bulk upload of
EAD to be done by the site administrator: it's going to be system intensive
so it should be done at a period of "low" traffic, and it may be best to
run the bulk load from the command line to avoid some of the pitfalls of
long-running HTTP requests.
On the other hand allowing upload of individual EAD records seems like a
great feature for the end-user and would require the ACL permissions you
describe.
--
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.
