I am trying to create a new XSD schema for my metadata and I am usign the XSD HTML Match editor! To do that, I am trying to see as examples what you have done with the MODS or OAI DC case in order to do the same and I encountered some problems and questions:
1) In OAI DC case you are using an XSD schema that is different from the one given in OAI site. Moreover, this schema is not valid. You declare an xs namespace and then you say xsd:string! Is that a mistace? Do you have in Fez a validator for the XSDs you are using?
2) Supposing that I create my new XSD display which is like DC with more elements. Then, I go to the Fedora Object Model and I clone the Image Mods 1.0 XSD display. In my new display, I add another looping element and inside xmlContent I declare the XSD reference to be the one I have created. Everything work fine so far. If I delete the MODS sublooping element then I get an error when I try to publish an object. And something more. If I try to create by my own a foxml file with a datastream of my new xmlContent, when FEZ indexes this item from Fedora, will read the metadata of this type??? I have tested it and the answer is no! But I need your confirmation!
Best regards,
Kostas Stamatis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fez won't index items that aren't in the content models. Furthermore, you shouldn't try and edit objects through Fez that have elements that aren't modelled in the XSD matching thing as you will porbably lose data (but it's safe if the entire dataastream is not used in Fez.)
matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did not quite understand your answer!
I create a new content model (as the ones you have created... MODS, OAI DC, MARCXML... etc). Actually, my content model named, say "KostasCM" is an extended Dublin Core. Then, I create XSD displays inside this Content Model for Image and Journal. That is, I see the schema tree, and I declare each element to be a textInput or whatever.
Then, I go back to Content Models and I click the fedora object thing that is the parent for all. There, I clone the MODS xsd display,in order to have a base and in this display I add a sublooping element named KostasMC. When I create an object I can see in fedora that the new datastream is created and it has the info from the form. It has many datastreams, like FezMD, FezACML, DC, KostasMC, MODS etc... I want know to do the reverse! Have a foxml file with KostasMC datastream and ingest it in Fedora. I do this, but when I index it in Fez it does not read the info from this KostasMC datastream.
I say that because, if i create a foxml file with a datastrean named MODS, when i index it in Fez it reads the metadata from MODS datastream!
Thank you for your response.
Kostas Stamatis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To do that you must choose 'index Fedora objects Into Fez' from the management screens in Fez. At that stage you can tell Fez which content model the fedora objects are using.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear all,
I am trying to create a new XSD schema for my metadata and I am usign the XSD HTML Match editor! To do that, I am trying to see as examples what you have done with the MODS or OAI DC case in order to do the same and I encountered some problems and questions:
1) In OAI DC case you are using an XSD schema that is different from the one given in OAI site. Moreover, this schema is not valid. You declare an xs namespace and then you say xsd:string! Is that a mistace? Do you have in Fez a validator for the XSDs you are using?
2) Supposing that I create my new XSD display which is like DC with more elements. Then, I go to the Fedora Object Model and I clone the Image Mods 1.0 XSD display. In my new display, I add another looping element and inside xmlContent I declare the XSD reference to be the one I have created. Everything work fine so far. If I delete the MODS sublooping element then I get an error when I try to publish an object. And something more. If I try to create by my own a foxml file with a datastream of my new xmlContent, when FEZ indexes this item from Fedora, will read the metadata of this type??? I have tested it and the answer is no! But I need your confirmation!
Best regards,
Kostas Stamatis
Fez won't index items that aren't in the content models. Furthermore, you shouldn't try and edit objects through Fez that have elements that aren't modelled in the XSD matching thing as you will porbably lose data (but it's safe if the entire dataastream is not used in Fez.)
matt
Dear Matt,
I did not quite understand your answer!
I create a new content model (as the ones you have created... MODS, OAI DC, MARCXML... etc). Actually, my content model named, say "KostasCM" is an extended Dublin Core. Then, I create XSD displays inside this Content Model for Image and Journal. That is, I see the schema tree, and I declare each element to be a textInput or whatever.
Then, I go back to Content Models and I click the fedora object thing that is the parent for all. There, I clone the MODS xsd display,in order to have a base and in this display I add a sublooping element named KostasMC. When I create an object I can see in fedora that the new datastream is created and it has the info from the form. It has many datastreams, like FezMD, FezACML, DC, KostasMC, MODS etc... I want know to do the reverse! Have a foxml file with KostasMC datastream and ingest it in Fedora. I do this, but when I index it in Fez it does not read the info from this KostasMC datastream.
I say that because, if i create a foxml file with a datastrean named MODS, when i index it in Fez it reads the metadata from MODS datastream!
Thank you for your response.
Kostas Stamatis
To do that you must choose 'index Fedora objects Into Fez' from the management screens in Fez. At that stage you can tell Fez which content model the fedora objects are using.