|
Hi, I am looking at the OAI provider service and I have the
following question: Does the service only cover DC metadata, or if any other designated
datastream possible? I am using a special datastream for Geosciences metadata
(FGDC standard), and I like that metadata to become available via OAI-PMH, so I
am wondering if the ProAI Service can support that. Thanks, -Jerry ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Jerry The service can be configured to cover any metadata you need. We serve up both DC and a UK thesis speciality called ‘UKETD_DC’ to which list we shall shortly add MODS. It’s all configurable. ___________________________________________________________________ Richard Green Consultant to Library & Learning Innovation, University of Hull managing the CLIF, Hydrangea in Hull and Hydra (Hull) Projects http://edocs.hull.ac.uk http://www.hull.ac.uk/clif http://hydrangeainhull.wordpress.com https://wiki.duraspace.org/display/hydra From: Pan, Jerry Yun [mailto:[hidden email]] Hi, I am looking at the OAI provider service and I have the following question: Does the service only cover DC metadata, or if any other designated datastream possible? I am using a special datastream for Geosciences metadata (FGDC standard), and I like that metadata to become available via OAI-PMH, so I am wondering if the ProAI Service can support that. Thanks, -Jerry ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Hi Richard,
We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver.fedora.md.formats = test_format formatX formatY oai_dc fgdc driver.fedora.md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a http://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadata we get <OAI-PMH xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-14T11:12:25Z</responseDate><request verb="ListRecords">http://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva |
|
In reply to this post by Richard Green
Hi Richard,
We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver.fedora.md.formats = test_format formatX formatY oai_dc fgdc driver.fedora.md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a http://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadata we get <OAI-PMH xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-14T11:12:25Z</responseDate><request verb="ListRecords">http://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva ________________________________________ From: Richard Green [[hidden email]] Sent: Thursday, March 24, 2011 1:04 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Jerry The service can be configured to cover any metadata you need. We serve up both DC and a UK thesis speciality called ‘UKETD_DC’ to which list we shall shortly add MODS. It’s all configurable. ___________________________________________________________________ Richard Green Consultant to Library & Learning Innovation, University of Hull managing the CLIF, Hydrangea in Hull and Hydra (Hull) Projects http://edocs.hull.ac.uk http://www.hull.ac.uk/clif http://hydrangeainhull.wordpress.com https://wiki.duraspace.org/display/hydra From: Pan, Jerry Yun [mailto:[hidden email]] Sent: 24 March 2011 4:30 PM To: [hidden email] Subject: [fcrepo-user] question on OAI-PMH Hi, I am looking at the OAI provider service and I have the following question: Does the service only cover DC metadata, or if any other designated datastream possible? I am using a special datastream for Geosciences metadata (FGDC standard), and I like that metadata to become available via OAI-PMH, so I am wondering if the ProAI Service can support that. Thanks, -Jerry ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
In reply to this post by ivashrestha
Two things spring to mind. First (apologies for asking) you have put
the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also http://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: [hidden email] Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver.fedora.md.formats = test_format formatX formatY oai_dc fgdc driver.fedora.md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a http://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">http://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: http://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Hi Richard,
http://localhost:8080/fedora/oai?verb=ListMetadataFormats returns oai_dc only. And now I have everything in capital case:: driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC driver.fedora.md.format.FGDC.dissType = info:fedora/*/FGDC.xml Can you explain a little more on oai entries into RELS-EXT because I have done no changes to RELS-EXT and I didn't find it mentioned in the documentation (sorry). Also just FYI we don't want to expose RELS-EXT. We want to expose the FGDC.xml datastream which is a Managed content Control Group. Sorry and Thank you, Biva ________________________________________ From: Richard Green [[hidden email]] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
I think what is happening then is that you are getting a spurious error
message. Each object that you want to expose must have an oai identifier in its RELS-EXT along the lines of: <oai:itemID>oai:hull.ac.uk:hull:1234</oai:itemID> We use oai: + domain name + PID. This identifier causes the object to be indexed by PROAI. Without this no FGDC datastreams will have been indexed and this *may* be at the bottom of the problem. In the RELS-EXT you will also have to declare the extra namespace: xmlns:oai="http://www.openarchives.org/OAI/2.0/" Let's fix the missing identifiers first and take it from there. R -----Original Message----- From: Shrestha, Biva [mailto:[hidden email]] Sent: 15 June 2011 2:29 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, http://localhost:8080/fedora/oai?verb=ListMetadataFormats returns oai_dc only. And now I have everything in capital case:: driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC driver.fedora.md.format.FGDC.dissType = info:fedora/*/FGDC.xml Can you explain a little more on oai entries into RELS-EXT because I have done no changes to RELS-EXT and I didn't find it mentioned in the documentation (sorry). Also just FYI we don't want to expose RELS-EXT. We want to expose the FGDC.xml datastream which is a Managed content Control Group. Sorry and Thank you, Biva ________________________________________ From: Richard Green [[hidden email]] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
In reply to this post by Richard Green
Hello Richard,
First of all thank you so much for being patient. I am not clear yet as to why we need to add entries to the RDF. In the documentation of OAI-PMH (https://wiki.duraspace.org/display/FCSVCS/OAI+Provider+Service+1.2.1) it clearly says that it: 1) Supports any metadata format available through your Fedora Repository via a Datastream or dissemination service 2) Supports sets that are expressed as RDF relationships in your digital objects' RELS-EXT Datastreams as exposed via the Resource Index Are these two same thing or linked. Because we are trying to achieve the first one here not the second one. Again I really appreciate your patience and I would really appreciate if you could explain as to why we would need those entries in RELS-EXT when we are trying to achieve the support number one and not two. thank you so much Biva ________________________________________ From: Richard Green [[hidden email]] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Many repositories do not expose *all* their content for harvesting. The
oai item ID in the RELS-EXT is the hook that causes PROAI to index an item and serve it up. Your (2) below relates to OAI-PMH harvesting sets so that people can harvest (say) just your physics content rather than all of your exposed content. These sets are optional. Without the RELS-EXT entries PROAI will not expose anything. Richard -----Original Message----- From: Shrestha, Biva [mailto:[hidden email]] Sent: 15 June 2011 9:59 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Hello Richard, First of all thank you so much for being patient. I am not clear yet as to why we need to add entries to the RDF. In the documentation of OAI-PMH (https://wiki.duraspace.org/display/FCSVCS/OAI+Provider+Service+1.2.1) it clearly says that it: 1) Supports any metadata format available through your Fedora Repository via a Datastream or dissemination service 2) Supports sets that are expressed as RDF relationships in your digital objects' RELS-EXT Datastreams as exposed via the Resource Index Are these two same thing or linked. Because we are trying to achieve the first one here not the second one. Again I really appreciate your patience and I would really appreciate if you could explain as to why we would need those entries in RELS-EXT when we are trying to achieve the support number one and not two. thank you so much Biva ________________________________________ From: Richard Green [[hidden email]] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md.format.fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Thank you Richard
We have our RELS-EXT as such <rdf:RDF xmlns:fedora-model="info:fedora/fedora-system:def/model#" xmlns:oai="http://www.openarchives.org/OAI/2.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="info:fedora/demo:22"> <oai:itemID>demo:22</oai:itemID> <fedora-model:hasModel rdf:resource="info:fedora/fedora-system:ServiceDefinition-3.0"></fedora-model:hasModel> </rdf:Description> </rdf:RDF> We are testing this locally that is why we have pid only in line <oai:itemID>demo:22</oai:itemID> Also in the proai.properties file we have driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC driver.fedora.md.format.FGDC.dissType = info:fedora/*/RELS-EXT But still the ListMetadataFormats query only gives oai_dc. Is there anything that we are missing. Biva -----Original Message----- From: Richard Green [mailto:[hidden email]] Sent: Thursday, June 16, 2011 4:36 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Many repositories do not expose *all* their content for harvesting. The oai item ID in the RELS-EXT is the hook that causes PROAI to index an item and serve it up. Your (2) below relates to OAI-PMH harvesting sets so that people can harvest (say) just your physics content rather than all of your exposed content. These sets are optional. Without the RELS-EXT entries PROAI will not expose anything. Richard -----Original Message----- From: Shrestha, Biva [mailto:[hidden email]] Sent: 15 June 2011 9:59 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Hello Richard, First of all thank you so much for being patient. I am not clear yet as to why we need to add entries to the RDF. In the documentation of OAI-PMH (hxxps://wiki.duraspace.org/display/FCSVCS/OAI+Provider+Service+1 . 2 . 1) it clearly says that it: 1) Supports any metadata format available through your Fedora Repository via a Datastream or dissemination service 2) Supports sets that are expressed as RDF relationships in your digital objects' RELS-EXT Datastreams as exposed via the Resource Index Are these two same thing or linked. Because we are trying to achieve the first one here not the second one. Again I really appreciate your patience and I would really appreciate if you could explain as to why we would need those entries in RELS-EXT when we are trying to achieve the support number one and not two. thank you so much Biva ________________________________________ From: Richard Green [R.Green@hull . ac . uk] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md . format . fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC
driver.fedora.md.format.FGDC.dissType = info:fedora/*/RELS-EXT The second can't be right. Should be: driver.fedora.md.format.FGDC.dissType = info:fedora/*/FGDC ? Richard -----Original Message----- From: Shrestha, Biva [mailto:[hidden email]] Sent: 20 June 2011 5:26 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Thank you Richard We have our RELS-EXT as such <rdf:RDF xmlns:fedora-model="info:fedora/fedora-system:def/model#" xmlns:oai="http://www.openarchives.org/OAI/2.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="info:fedora/demo:22"> <oai:itemID>demo:22</oai:itemID> <fedora-model:hasModel rdf:resource="info:fedora/fedora-system:ServiceDefinition-3.0"></fedora- model:hasModel> </rdf:Description> </rdf:RDF> We are testing this locally that is why we have pid only in line <oai:itemID>demo:22</oai:itemID> Also in the proai.properties file we have driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC driver.fedora.md.format.FGDC.dissType = info:fedora/*/RELS-EXT But still the ListMetadataFormats query only gives oai_dc. Is there anything that we are missing. Biva -----Original Message----- From: Richard Green [mailto:[hidden email]] Sent: Thursday, June 16, 2011 4:36 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Many repositories do not expose *all* their content for harvesting. The oai item ID in the RELS-EXT is the hook that causes PROAI to index an item and serve it up. Your (2) below relates to OAI-PMH harvesting sets so that people can harvest (say) just your physics content rather than all of your exposed content. These sets are optional. Without the RELS-EXT entries PROAI will not expose anything. Richard -----Original Message----- From: Shrestha, Biva [mailto:[hidden email]] Sent: 15 June 2011 9:59 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Hello Richard, First of all thank you so much for being patient. I am not clear yet as to why we need to add entries to the RDF. In the documentation of OAI-PMH (hxxps://wiki.duraspace.org/display/FCSVCS/OAI+Provider+Service+1 . 2 . 1) it clearly says that it: 1) Supports any metadata format available through your Fedora Repository via a Datastream or dissemination service 2) Supports sets that are expressed as RDF relationships in your digital objects' RELS-EXT Datastreams as exposed via the Resource Index Are these two same thing or linked. Because we are trying to achieve the first one here not the second one. Again I really appreciate your patience and I would really appreciate if you could explain as to why we would need those entries in RELS-EXT when we are trying to achieve the support number one and not two. thank you so much Biva ________________________________________ From: Richard Green [R.Green@hull . ac . uk] Sent: Wednesday, June 15, 2011 5:26 AM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Two things spring to mind. First (apologies for asking) you have put the appropriate oai entries into the RELS-EXT of each object haven't you (<oai:itemID>)? Second, I wonder if there is some case sensitivity - you have both FGDC and fgdc: I wonder if they should all match? Try also hxxp://localhost:8080/fedora/oai?verb=ListMetadataFormats and see if it returns fgdc. R -----Original Message----- From: ivashrestha [mailto:[hidden email]] Sent: 14 June 2011 8:35 PM To: fedora-commons-users@lists . sourceforge . net Subject: Re: [fcrepo-user] question on OAI-PMH Hi Richard, We have a datastream with DSID "FGDC.xml" and content as follows: <metadata> [xml-content] </metadata> We want to expose this datastream using OAI-PMH support. And the changes that we added to the proai.properties file are driver . fedora . md.formats = test_format formatX formatY oai_dc fgdc driver . fedora . md . format . fgdc.dissType = info:fedora/*/FGDC.xml After these changes the datastream is still not being exposed because when we do a hxxp://localhost:8080/fedora/oai?verb=ListRecords&metadataPrefix=metadat a we get <OAI-PMH xsi:schemaLocation="hxxp://www.openarchives.org/OAI/2.0/ hxxp://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2011-06-1 4T11:12:25Z</responseDate><request verb="ListRecords">hxxp://localhost:8080/fedora/oai</request><error code="cannotDisseminateFormat">Repository does not provide that format in OAI-PMH responses.</error></OAI-PMH> Is there something we are missing? thank you so much Biva -- View this message in context: hxxp://fedora-commons.1317035.n2.nabble.com/fcrepo-user-question-on-OAI- PMH-tp6204787p6475611.html Sent from the Fedora Commons Users mailing list archive at Nabble.com. ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. hxxp://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists . sourceforge . net hxxps://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------ ------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Hi,
On Thu, Jun 23, 2011 at 11:56 AM, Richard Green <[hidden email]> wrote: > driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC > driver.fedora.md.format.FGDC.dissType = info:fedora/*/RELS-EXT > > The second can't be right. Should be: > > driver.fedora.md.format.FGDC.dissType = info:fedora/*/FGDC ? If the record you want to deliver is in the FGDC datastream (and it's called exactly that in the target objects), that setting above would tell proai what to look for. But earlier, Biva indicated that it's actually the FGDC.xml datastream. If that's the ID that's used in the objects, then that's what you need to have at the end of this configuration item. Another thing to check: I believe you'll also need to have defined the following properties: driver.fedora.md.format.FGDC.uri = (the XML namespace URI of the format you're delivering) driver.fedora.md.format.FGDC.loc = (the URL of the schema of that format) For example, I just stumbled on the following post that shows how Emory added a few formats to their oai provider configuration: https://techknowhow.library.emory.edu/etd-documentation/fedora-oai-provider-configuration-etd If fixing the datastream id in the .dissType setting and adding the above two additional configuration values doesn't do the trick, can you check the log file for any WARN or ERROR entries? - Chris ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
|
Thanks, Chris!
R -----Original Message----- From: Chris Wilper [mailto:[hidden email]] Sent: 23 June 2011 6:07 PM To: Support and info exchange list for Fedora users. Subject: Re: [fcrepo-user] question on OAI-PMH Hi, On Thu, Jun 23, 2011 at 11:56 AM, Richard Green <[hidden email]> wrote: > driver.fedora.md.formats = test_format formatX formatY oai_dc FGDC > driver.fedora.md.format.FGDC.dissType = info:fedora/*/RELS-EXT > > The second can't be right. Should be: > > driver.fedora.md.format.FGDC.dissType = info:fedora/*/FGDC ? If the record you want to deliver is in the FGDC datastream (and it's called exactly that in the target objects), that setting above would tell proai what to look for. But earlier, Biva indicated that it's actually the FGDC.xml datastream. If that's the ID that's used in the objects, then that's what you need to have at the end of this configuration item. Another thing to check: I believe you'll also need to have defined the following properties: driver.fedora.md.format.FGDC.uri = (the XML namespace URI of the format you're delivering) driver.fedora.md.format.FGDC.loc = (the URL of the schema of that format) For example, I just stumbled on the following post that shows how Emory added a few formats to their oai provider configuration: https://techknowhow.library.emory.edu/etd-documentation/fedora-oai-provider-configuration-etd If fixing the datastream id in the .dissType setting and adding the above two additional configuration values doesn't do the trick, can you check the log file for any WARN or ERROR entries? - Chris ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ***************************************************************************************** To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html ***************************************************************************************** ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Fedora-commons-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users |
| Powered by Nabble | Edit this page |
