Content metadata display in Share .docx

[stevegreenbaum]

When a .docx is uploaded, the list of properties that appears on the Share preview screen is different than I normally see for a .doc.  I upload a .doc and then a .docx – both documents are type cm:content, why the difference?  Is the extractor capturing more data for the docx? 

In the docx property list, there are elements present from the lockable aspect, but I don’t see the lockable aspect defined in share-form-config.xml.     Why do they still appear?

For a docx, the following properties appear:

Node DB Identifier: 1,822
Store Identifier: SpacesStore
Version Label: 1.4
Lock Owner:
Deep Lock: No
Auto Version: Yes
Expiry Date: Mon 19 Jul 2010
Last Accessed Date:
Title: Document2.docx
Author: admin
Modified Date: Mon 19 Jul 2010 18:17:26
Node Identifier: f6b31154-15bc-4fe7-9bcc-d2e728633ede
Created Date: Thu 15 Jul 2010 23:44:10
Lock Type:
Store Protocol: workspace
Creator: admin
Description:
Modifier: admin
Initial Version: Yes
rn:rendition: doclib webpreview
Mimetype: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Encoding: utf-8


Typical .doc metadata:

Name: New Microsoft Office Word Document.doc
Title: New Microsoft Office Word Document.doc
Description:
Mimetype: Microsoft Word
Author: admin
Size: 22 KB
Creator: admin
Created Date: Thu 15 Jul 2010 19:26:02
Modifier: admin
Modified Date: Mon 19 Jul 2010 13:27:38

[mikeh]

The .docx is using a default form, not the standard one for cm:content. Have you got some custom modelling going on?

Thanks,
Mike

[stevegreenbaum]

Yes, there is custom modeling.  I now see that for one of my custom Types I didn't have a definition in share-config-custom.xml, so that explains it.  I always get the default form for that type. 

There are some documents uploaded several weeks ago that are content type of cm:content that are still showing up with the default form as well, but I likely had some configuration problem then that has since been resolved because new .docx documents uploaded appear with the correct cm:content form. I don't understand why these older cm:content documents, still comes up with the default form.  Looking at the node browser I notice it has the lockable aspect, whereas nodes that are appearing correctly do not have this aspect.