Hi Elvi,
the demo.dspace.org OAI Data provider also has this bug. I've requested
your OAI interface
http://repository.seafdec.org.ph/oai/request?verb=ListRecords&metadataPrefix=qdc
and
it seems the XSL I sent you isn't in use. Are you sure you replaced at the
right place?
On 5 June 2013 17:27, Nemiz, Elvi <[email protected]> wrote:
> Dear João,
>
> I still got the same results. I followed step 1, submitted a sample item
> and after accepting it I changed the content source from standard dspace
> collection to harvesting. Restarted the OAI-PMH source and executed oai
> import clean-cache command. I wonder if this only affects dspace 3.x since
> I also got the same results if I changed the OAI Provider to
> http://demo.dspace.org/oai/request?
>
>
> On Thu, Jun 6, 2013 at 12:05 AM, João Melo <[email protected]> wrote:
>
>> *3rd step - Run the "dspace oai clean-cache" command
>>
>>
>> On 5 June 2013 16:37, João Melo <[email protected]> wrote:
>>
>>> Elvi,
>>>
>>> try the following procedure:
>>>
>>> 1. Remove the OAI-PMH configuration from your collection, save it as a
>>> normal collection and then configure the OAI-PMH source again (so then it
>>> will run the process from the start).
>>>
>>> 2. Restart the OAI-PMH server - the server which is the OAI-PMH source
>>> (just restart/reload tomcat).
>>>
>>> The import command:
>>>
>>> The -c flag will remove all previously indexed records. It's not
>>> recommended to add this flag (it was made available only to manual use of
>>> the indexing operation - special ocasiation which must index everything
>>> again).
>>>
>>>
>>>
>>> On 5 June 2013 16:31, Nemiz, Elvi <[email protected]> wrote:
>>>
>>>> Hello João,
>>>>
>>>> I tested the qdc.xsl and harvesting is still unsuccessful. By the way,
>>>> even if I selected simple dublin core or DIM as the Metadata format, I
>>>> still got the Last Harvest Result: OAI server did not contain any updates,
>>>> etc. Checking inside the /var/oai/requests directory, I still have
>>>> the <error code="noRecordsMatch">No matches for the query</error> message.
>>>> Also as noted by helix, how often should I run import oai -c if running it
>>>> nightly is not recommended?
>>>>
>>>> Thanks for looking at this issue.
>>>>
>>>> Regards,
>>>> Elvi
>>>>
>>>>
>>>> On Wed, Jun 5, 2013 at 7:59 PM, João Melo <[email protected]> wrote:
>>>>
>>>>> Sending a new version with a tiny change (just for validation
>>>>> purposes).
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 5 June 2013 12:50, João Melo <[email protected]> wrote:
>>>>>
>>>>>> Elvi,
>>>>>>
>>>>>> could you test the qdc.xsl sent in attachment?
>>>>>> Replace the <dspace>/config/crosswalks/oai/metadataFormats/qdc.xsl
>>>>>> file by this one.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> On 5 June 2013 12:29, João Melo <[email protected]> wrote:
>>>>>>
>>>>>>> Hi Elvi,
>>>>>>>
>>>>>>> from my analysis, the QDC crosswalk is expecting a root element
>>>>>>> named qualifieddc, in fact, the current DSpace OAI (service) doesn't
>>>>>>> exposes it. To fix this it's only required to change the qdc xslt
>>>>>>> crosswalk
>>>>>>> (configuration file). However, I'm going to take a deeper look at it, I
>>>>>>> think I am able to come up with a solution in few days.
>>>>>>>
>>>>>>>
>>>>>>> On 5 June 2013 10:44, Nemiz, Elvi <[email protected]> wrote:
>>>>>>>
>>>>>>>> Dear All,
>>>>>>>>
>>>>>>>> I'm wondering if someone from dspace-tech list have actually
>>>>>>>> harvested items from demo.dspace.org? Please see the end of this
>>>>>>>> thread:
>>>>>>>> http://dspace.2283337.n4.nabble.com/Harvesting-OAI-ORE-via-XMLUI-interface-v2-td4664539.htmlif
>>>>>>>> there's something I have missed. Also, I can't harvest from our
>>>>>>>> production server to my test server. I am running a scheduled task of
>>>>>>>> "dspace oai import -c -o" every night in our production server running
>>>>>>>> dspace 3.0. I have a fresh install of dspace 3.1 for my test server
>>>>>>>> and I
>>>>>>>> have no luck harvesting from our production server. I am asking this
>>>>>>>> because a collection administrator of another repository told me that
>>>>>>>> their
>>>>>>>> submitters were submitting items to their repository "manually (this
>>>>>>>> includes downloading our bitstreams and uploading them which can
>>>>>>>> easily be
>>>>>>>> done by setting Harvesting Options to Harvest metadata and references
>>>>>>>> to
>>>>>>>> bitstreams)". So I advised her to just harvest content from our
>>>>>>>> repository
>>>>>>>> via OAI and now I found out that I can't even harvest from our own
>>>>>>>> repository. If someone can test harvest our repository, please inform
>>>>>>>> me if
>>>>>>>> you are successful and what steps do I have to take to harvest
>>>>>>>> successfully. Please also advice what configurations do I have to set
>>>>>>>> to
>>>>>>>> our production server so that our content can be harvested
>>>>>>>> successfully.
>>>>>>>> Here's our repository's specific sets:
>>>>>>>> http://repository.seafdec.org.ph/oai/request?verb=ListSets.
>>>>>>>>
>>>>>>>> Thanks in advance and regards,
>>>>>>>> elvi
>>>>>>>
>>>>>>>
--
Thanks, João Melo (My Portfolio <http://www.lyncode.com/m/jmelo/>)
DSpace Department
*Lyncode*: Official
website<http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2F&sa=D&sntz=1&usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ>
[image: Follow us on
Facebook]<http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q>
<http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncode&sa=D&sntz=1&usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww>
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette