I managed to add my new content model, and everything works fine! I mean, I can go to the collection, see the form with the new elements of my Content Model, it is stored in Fedora. If I go directly to Fedora, I can see the new datastream as I have defined it in my XSD, everything ok.
But, when i click the item, i cannot see these new elements, even if I have clicked the checkbox that says: "Show in View Details?". Also, when I try to edit this item, the specific textboxes are empty, although the FOXML containts my datastream with these element, as I said!
Can you please explain a little bit what are all these configuration in the Mapping? (Attached XSDMF ID:, Use in HTML Meta Header?:, HTML Meta Header Name: ... etc)?
I am looking forward for your response!
Cheers,
Kostas Stamatis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It sounds like this might be because the branches in the XSD tree above the elements that you want to show need to be set as 'Static text' and just leave the static text entry box blank. It's a bit of a kludge but otherwise the XSD thing won't look at the sub-elements.
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry for the delayed response, but yesterday I was out of the office!
In which XSD need to do that? In the Foxml or my Content Model's XSD? Because in my XSD, there is only the root element above the elements I want to show!
Actually, see below what the part of my content model in the Foxml file looks like:
I have sent you an email with the xsd Display.
I think that you are right, the namespaces are the problem because I tested a very very simple xsd without namespaces and it works fine. But i do the same things as in the OAI DC case... so I cannot see the difference.
Please, if you find time check the email and the XSD display! Maybe, a second eye can see the problem!
Cheers,
Kostas Stamatis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Matt,
I managed to add my new content model, and everything works fine! I mean, I can go to the collection, see the form with the new elements of my Content Model, it is stored in Fedora. If I go directly to Fedora, I can see the new datastream as I have defined it in my XSD, everything ok.
But, when i click the item, i cannot see these new elements, even if I have clicked the checkbox that says: "Show in View Details?". Also, when I try to edit this item, the specific textboxes are empty, although the FOXML containts my datastream with these element, as I said!
Can you please explain a little bit what are all these configuration in the Mapping? (Attached XSDMF ID:, Use in HTML Meta Header?:, HTML Meta Header Name: ... etc)?
I am looking forward for your response!
Cheers,
Kostas Stamatis
Kostas,
It sounds like this might be because the branches in the XSD tree above the elements that you want to show need to be set as 'Static text' and just leave the static text entry box blank. It's a bit of a kludge but otherwise the XSD thing won't look at the sub-elements.
Matt
Dear Matt,
sorry for the delayed response, but yesterday I was out of the office!
In which XSD need to do that? In the Foxml or my Content Model's XSD? Because in my XSD, there is only the root element above the elements I want to show!
Actually, see below what the part of my content model in the Foxml file looks like:
</foxml:datastream>
<foxml:datastream ID="Pandektis" STATE="A" CONTROL_GROUP="X" VERSIONABLE="true">
<foxml:datastreamVersion ID="Pandektis1.0" LABEL="Pandektis Record" CREATED="2007-06-27T07:04:55.685Z" MIMETYPE="text/xml" SIZE="491">
<foxml:contentDigest TYPE="DISABLED" DIGEST="none"/>
<foxml:xmlContent>
It seems good to me!
Do you have any other idea?
Thank you very much in advance!
Cheers,
Kostas Stamatis
Maybe Fez is having trouble with the namespaces. Can you send me your XSD Display using the export XSDs as XML function the Administration panel?
Matt
Dear Matt,
I have sent you an email with the xsd Display.
I think that you are right, the namespaces are the problem because I tested a very very simple xsd without namespaces and it works fine. But i do the same things as in the OAI DC case... so I cannot see the difference.
Please, if you find time check the email and the XSD display! Maybe, a second eye can see the problem!
Cheers,
Kostas Stamatis