Difference between revisions of "Talk:PubMan File Properties"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=== Status === | === Status === | ||
The file-size will be removed from the properties - that means we need to create it in our file metadata record. But on the other hand side, keeping only file-size in the metadata record as a single metadata makes no sense to me. So the | The file-size will be removed from the properties - that means we need to create it in our file metadata record. But on the other hand side, keeping only file-size in the metadata record as a single metadata makes no sense to me. So the questions are: | ||
# shall we stick with the file size only in the metadata record | # shall we stick with the file size only in the metadata record | ||
# shall we put the file size and redundantly keep as well properties in the metadata record (may be important for things like LTA, dissemination) | # shall we put the file size and redundantly keep as well properties in the metadata record (may be important for things like LTA, dissemination) | ||
: Are there any use cases in which the framework change a component property? Or is this only done by application, thus can the application ensure that redundant data are synchronized? --[[User:Inga|Inga]] 11:31, 15 May 2008 (CEST) | |||
: For items we already split information between metadata record and property (e.g. the item status/identifier) is in the properties while descriptive information is in the metadata record. This would be fine for files too - if we have a common understanding about what characterize a property and what characterize an attribute in the metadata (see below) --[[User:Inga|Inga]] 11:31, 15 May 2008 (CEST) | |||
# shall we remove the file size completely from the metadata record | # shall we remove the file size completely from the metadata record | ||
=== Further questions === | === Further questions === | ||
* Could somebody please explain why the file size should be removed from properties, thus which characteristic makes an information | * Could somebody please explain why the file size should be removed from properties, thus which characteristic makes an information to a property? --[[User:Inga|Inga]] 11:31, 15 May 2008 (CEST) | ||
* How would the object look like? Item xsd with one metadata record and additional metadata records for each component? | |||
Revision as of 09:31, 15 May 2008
Component properties and/or file metadata record?[edit]
Resources[edit]
- file properties which are defined and maintained by Framework: http://www.escidoc-project.de/schemas/soap/item/0.6/components.xsd
- escidoc application profile file: http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Application_Profile_File
Status[edit]
The file-size will be removed from the properties - that means we need to create it in our file metadata record. But on the other hand side, keeping only file-size in the metadata record as a single metadata makes no sense to me. So the questions are:
- shall we stick with the file size only in the metadata record
- shall we put the file size and redundantly keep as well properties in the metadata record (may be important for things like LTA, dissemination)
- Are there any use cases in which the framework change a component property? Or is this only done by application, thus can the application ensure that redundant data are synchronized? --Inga 11:31, 15 May 2008 (CEST)
- For items we already split information between metadata record and property (e.g. the item status/identifier) is in the properties while descriptive information is in the metadata record. This would be fine for files too - if we have a common understanding about what characterize a property and what characterize an attribute in the metadata (see below) --Inga 11:31, 15 May 2008 (CEST)
- shall we remove the file size completely from the metadata record
Further questions[edit]
- Could somebody please explain why the file size should be removed from properties, thus which characteristic makes an information to a property? --Inga 11:31, 15 May 2008 (CEST)
- How would the object look like? Item xsd with one metadata record and additional metadata records for each component?