|
⇤ ← Revision 1 as of 2008-06-26 12:26:15
Size: 1264
Comment: Created by the PackagePages action.
|
← Revision 2 as of 2010-03-17 13:09:14 ⇥
Size: 1264
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| * ["DOMS objects"]. * ["SB DOMS object structure"]. * ["DOMS Content Model"] * ["DOMS terminology"]. * ["Ensuring integrity"] * ["OAIS conflicts"] * ["Projects at SB"] * ["DOMS data formats"] * ["Bitstorage"] * ["Test platform"] * ["Tools"] |
* [[DOMS objects]]. * [[SB DOMS object structure]]. * [[DOMS Content Model]] * [[DOMS terminology]]. * [[Ensuring integrity]] * [[OAIS conflicts]] * [[Projects at SB]] * [[DOMS data formats]] * [[Bitstorage]] * [[Test platform]] * [[Tools]] |
Misc.
How do we handle object renaming?
Case: In the "Reklamefilm"-project, each work is assigned an ID in the style of mc:Commercial_1234. This ID is used for referencing the object. At a later date, it is decided, that the ID mc:Commercial_Colgate1975 is better.
Suggestion1: We create a new object, update references to it and mark the old object as deleted.
Problem1: We can't update external references, so they will be invalidated.
Suggestion2: We create a new object, update references to it and let the old object point to the new object.
Problem2: We need a mechanism to ensure that the old object isn't indexed. Maybe we need that anyway?
Suggestion3: We do not use the internal object ID for external references. Instead we provide a list of ID's, that can be used for referencing the object.
Problem3: This will probably hurt performance, at the request of a single object will require at least two lookups.