Difference between revisions of "Talk:ESciDoc Version History Event Type"
Jump to navigation
Jump to search
(→Tasks) |
(→Tasks) |
||
| Line 10: | Line 10: | ||
** e.g. just an eventType for update or seperate ones for updateProperties, updateMdRecords, etc. | ** e.g. just an eventType for update or seperate ones for updateProperties, updateMdRecords, etc. | ||
*** Possibly misleading: calling update may just modify Properties which is an equivalent operation to updateProperties. [[User:Frank|Frank]] 10:09, 2 February 2010 (UTC) | *** Possibly misleading: calling update may just modify Properties which is an equivalent operation to updateProperties. [[User:Frank|Frank]] 10:09, 2 February 2010 (UTC) | ||
*** From [[ESciDoc_Committer_Meeting_2010-02-02|TelCo]]: Maybe necessary to track exactly which service method was called. | |||
** Differentiate between resources (updateItem, updateContainer, etc.)? | ** Differentiate between resources (updateItem, updateContainer, etc.)? | ||
*** Unnecessary because the event is related to an Item or Container or ... Semantically no difference (e.g. resource is updated). But the range of what is possibly modified changes. What actually changes is not tracked even when differentiate resource-type. Just blows up the list of eventTypes. [[User:Frank|Frank]] 09:54, 2 February 2010 (UTC) | *** Unnecessary because the event is related to an Item or Container or ... Semantically no difference (e.g. resource is updated). But the range of what is possibly modified changes. What actually changes is not tracked even when differentiate resource-type. Just blows up the list of eventTypes. [[User:Frank|Frank]] 09:54, 2 February 2010 (UTC) | ||
**** Agreed on [[ESciDoc_Committer_Meeting_2010-02-02|TelCo]]. | |||
* Create an informal list of eventTypes. | * Create an informal list of eventTypes. | ||
** MPDL proposes to list the service methods. | ** MPDL proposes to list the service methods. | ||
| Line 17: | Line 19: | ||
* Strings or URIs? | * Strings or URIs? | ||
** How to publish the vocabulary? | ** How to publish the vocabulary? | ||
** From [[ESciDoc_Committer_Meeting_2010-02-02|TelCo]]: URI seems to be good; can be escidoc PURL managed by MPDL. | |||
* How and when implemented? | * How and when implemented? | ||
Latest revision as of 16:44, 2 February 2010
In respect to the premis examples:
create -> creation update -> modification
Tasks[edit]
- How detailed?
- e.g. just an eventType for update or seperate ones for updateProperties, updateMdRecords, etc.
- Differentiate between resources (updateItem, updateContainer, etc.)?
- Unnecessary because the event is related to an Item or Container or ... Semantically no difference (e.g. resource is updated). But the range of what is possibly modified changes. What actually changes is not tracked even when differentiate resource-type. Just blows up the list of eventTypes. Frank 09:54, 2 February 2010 (UTC)
- Agreed on TelCo.
- Unnecessary because the event is related to an Item or Container or ... Semantically no difference (e.g. resource is updated). But the range of what is possibly modified changes. What actually changes is not tracked even when differentiate resource-type. Just blows up the list of eventTypes. Frank 09:54, 2 February 2010 (UTC)
- Create an informal list of eventTypes.
- Strings or URIs?
- How to publish the vocabulary?
- From TelCo: URI seems to be good; can be escidoc PURL managed by MPDL.
- How and when implemented?
A decision should be made next Committer Meeting.
List of eventTypes following service methods[edit]
All available service methods modifying a resource:
create delete (?) update submit release revise withdraw assignObjectPid assignVersionPid assignContentPid lock unlock
What about (possibly) future methods modifying sub-resources? E.g.:
createComponent createMdRecord updateComponent updateMdRecord moveToContext