Re: [dspace-community] Re: Moving all the items from one collection to another

2017-02-19 Thread Olivier 
OK, I am replying to myself...

On FreeBSD, when upgrading tomcat, the ownership of the tomcat
installation directory is reset to some predefined www user, instead of
the tomcat user, so the temp directory became unavailable and indexing
would fail.

Solve now, thanks for the replies.

Olivier

>> To completely rebuild the index you should use "./dspace index-discovery
>> -b".  This is documented in the Discovery maintenance guidelines here:
>> https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-DiscoverySolrIndexMaintenance
>
> I tried index-discovery -b but I still have indexes showin only about
> 10% of the items: see https://www.cs.ait.ac.th/xmlui/handle/123456789/91
> and the collection it belogs to
> https://www.cs.ait.ac.th/xmlui/handle/123456789/18
>
> I am lost here.
>
> Best regards,
>
> Olivier
>
>>
>> - Tim
>>
>> On Fri, Feb 17, 2017 at 3:07 AM Olivier  wrote:
>>
>>> Help!
>>>
>>> > If the item (in the item view) says it is in the new collection, It is...
>>> >
>>> > So,  you probably are experiencing either a cache problem or your
>>> > indexes are now being updated.  For solving the second issue, try a
>>> > index-discovery reindex. Probably a complete rebuild is the best option
>>> > in your case.dspace index-discovery -f from the command line
>>> > interface
>>>
>>> It has gone worth, I have gone from 600 items to 78, most of the
>>> collections are empty after an index-discovery -f
>>>
>>> TIA,
>>>
>>> Olivier
>>>
>>> >
>>> > best luck
>>> >
>>> > Emilio
>>> >
>>> >
>>> >
>>> > El 17/02/2017 a las 5:34, Olivier escribió:
>>> >> Emilio,
>>> >>
>>> >>> The easiest way (apart of direct database handling) is Batch
>>> Metadata=20
>>> >>> editing.
>>> https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing
>>> >>>
>>> >>> Export the collection to csv, edit the collection handle and import
>>> the csv
>>> >> I tried that and it appears to work fine... but. When I display the
>>> >> Communities & Collections pages, the items that have been moved are not
>>> >> counted in the new collection: old and new collections are listed with
>>> >> zero items.
>>> >>
>>> >> If I access the items with their handle, I can see they are belong to
>>> >> the new collection.
>>> >>
>>> >> I also have the problem with an item submited yesterday, to a different
>>> >> collection. The different collection does not show the item, but the
>>> >> item shows it belongs to that different collection.
>>> >>
>>> >> Is there a secert command to get DSpace regenerate the index of the
>>> >> collections?
>>> >>
>>> >> Best regards,
>>> >>
>>> >> Olivier
>>> >>
>>> >>> regards
>>> >>> Emilio
>>> >>>
>>> >>> El 16/02/2017 a las 11:54, Olivier escribi=C3=B3:
>>>  Hello,
>>> 
>>>  is there an easy way, in DSpace 4.2 (I don't want to update because we
>>>  should soon have a shinny centralized DSpace) a way to move all the
>>>  items from one collection to another?
>>> 
>>>  Best regards,
>>> 
>>>  Olivier
>>>
>>> --
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "DSpace Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to dspace-community+unsubscr...@googlegroups.com.
>>> To post to this group, send email to dspace-community@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-community.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>>
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
> -- 

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-community] Re: Moving all the items from one collection to another

2017-02-19 Thread Olivier 
Hi Tim,

> To completely rebuild the index you should use "./dspace index-discovery
> -b".  This is documented in the Discovery maintenance guidelines here:
> https://wiki.duraspace.org/display/DSDOC5x/Discovery#Discovery-DiscoverySolrIndexMaintenance

I tried index-discovery -b but I still have indexes showin only about
10% of the items: see https://www.cs.ait.ac.th/xmlui/handle/123456789/91
and the collection it belogs to
https://www.cs.ait.ac.th/xmlui/handle/123456789/18

I am lost here.

Best regards,

Olivier

>
> - Tim
>
> On Fri, Feb 17, 2017 at 3:07 AM Olivier  wrote:
>
>> Help!
>>
>> > If the item (in the item view) says it is in the new collection, It is...
>> >
>> > So,  you probably are experiencing either a cache problem or your
>> > indexes are now being updated.  For solving the second issue, try a
>> > index-discovery reindex. Probably a complete rebuild is the best option
>> > in your case.dspace index-discovery -f from the command line
>> > interface
>>
>> It has gone worth, I have gone from 600 items to 78, most of the
>> collections are empty after an index-discovery -f
>>
>> TIA,
>>
>> Olivier
>>
>> >
>> > best luck
>> >
>> > Emilio
>> >
>> >
>> >
>> > El 17/02/2017 a las 5:34, Olivier escribió:
>> >> Emilio,
>> >>
>> >>> The easiest way (apart of direct database handling) is Batch
>> Metadata=20
>> >>> editing.
>> https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing
>> >>>
>> >>> Export the collection to csv, edit the collection handle and import
>> the csv
>> >> I tried that and it appears to work fine... but. When I display the
>> >> Communities & Collections pages, the items that have been moved are not
>> >> counted in the new collection: old and new collections are listed with
>> >> zero items.
>> >>
>> >> If I access the items with their handle, I can see they are belong to
>> >> the new collection.
>> >>
>> >> I also have the problem with an item submited yesterday, to a different
>> >> collection. The different collection does not show the item, but the
>> >> item shows it belongs to that different collection.
>> >>
>> >> Is there a secert command to get DSpace regenerate the index of the
>> >> collections?
>> >>
>> >> Best regards,
>> >>
>> >> Olivier
>> >>
>> >>> regards
>> >>> Emilio
>> >>>
>> >>> El 16/02/2017 a las 11:54, Olivier escribi=C3=B3:
>>  Hello,
>> 
>>  is there an easy way, in DSpace 4.2 (I don't want to update because we
>>  should soon have a shinny centralized DSpace) a way to move all the
>>  items from one collection to another?
>> 
>>  Best regards,
>> 
>>  Olivier
>>
>> --
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-community+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-community@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-community.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-community] Re: Moving all the items from one collection to another

2017-02-17 Thread Olivier 
Help!

> If the item (in the item view) says it is in the new collection, It is...
>
> So,  you probably are experiencing either a cache problem or your 
> indexes are now being updated.  For solving the second issue, try a 
> index-discovery reindex. Probably a complete rebuild is the best option 
> in your case.dspace index-discovery -f from the command line 
> interface

It has gone worth, I have gone from 600 items to 78, most of the
collections are empty after an index-discovery -f

TIA,

Olivier

>
> best luck
>
> Emilio
>
>
>
> El 17/02/2017 a las 5:34, Olivier escribió:
>> Emilio,
>>
>>> The easiest way (apart of direct database handling) is Batch Metadata=20
>>> editing. https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing
>>>
>>> Export the collection to csv, edit the collection handle and import the csv
>> I tried that and it appears to work fine... but. When I display the
>> Communities & Collections pages, the items that have been moved are not
>> counted in the new collection: old and new collections are listed with
>> zero items.
>>
>> If I access the items with their handle, I can see they are belong to
>> the new collection.
>>
>> I also have the problem with an item submited yesterday, to a different
>> collection. The different collection does not show the item, but the
>> item shows it belongs to that different collection.
>>
>> Is there a secert command to get DSpace regenerate the index of the
>> collections?
>>
>> Best regards,
>>
>> Olivier
>>
>>> regards
>>> Emilio
>>>
>>> El 16/02/2017 a las 11:54, Olivier escribi=C3=B3:
 Hello,

 is there an easy way, in DSpace 4.2 (I don't want to update because we
 should soon have a shinny centralized DSpace) a way to move all the
 items from one collection to another?

 Best regards,

 Olivier

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-community] Re: Moving all the items from one collection to another

2017-02-17 Thread emilio lorenzo 

Olivier,

If the item (in the item view) says it is in the new collection, It is...

So,  you probably are experiencing either a cache problem or your 
indexes are now being updated.  For solving the second issue, try a 
index-discovery reindex. Probably a complete rebuild is the best option 
in your case.dspace index-discovery -f from the command line 
interface


best luck

Emilio



El 17/02/2017 a las 5:34, Olivier escribió:

Emilio,


The easiest way (apart of direct database handling) is Batch Metadata=20
editing. https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing

Export the collection to csv, edit the collection handle and import the csv

I tried that and it appears to work fine... but. When I display the
Communities & Collections pages, the items that have been moved are not
counted in the new collection: old and new collections are listed with
zero items.

If I access the items with their handle, I can see they are belong to
the new collection.

I also have the problem with an item submited yesterday, to a different
collection. The different collection does not show the item, but the
item shows it belongs to that different collection.

Is there a secert command to get DSpace regenerate the index of the
collections?

Best regards,

Olivier


regards
Emilio

El 16/02/2017 a las 11:54, Olivier escribi=C3=B3:

Hello,

is there an easy way, in DSpace 4.2 (I don't want to update because we
should soon have a shinny centralized DSpace) a way to move all the
items from one collection to another?

Best regards,

Olivier


--
You received this message because you are subscribed to the Google Groups "DSpace 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.