[dspace-tech] Re: Harvesting a DSpace 6.3 OAI server from a Dspace 5.10 client

2019-01-31 Thread Diego Brice


El viernes, 25 de enero de 2019, 11:31:03 (UTC-3), Diego Brice escribió:
>
> Hi!. I have problems trying to 
> harvest my DSpace 6.3 server. This is my scenario:
>
>
> I have a DSpace 6.3 repo with many communities and collections running in 
> an intranet environment. Some of those collection are private, so there is 
> no anonymous access. Some of the "public" collections must be shared with 
> outside people so this is the first problem I have to solve. Because there 
> is no way to hide communities and collections (I mean, you see the 
> collection listed and I don´t want to let the outside user know  that there 
> is a private collection) I thought that the best way to achieve this is to 
> have a second server where I create only those communities and collections 
> that are public and harvest records and documents from the main DSpace 
> server.
>
> After installing a second 6.3 server I got the second problem. There is an 
> unresolved bug that doesn´t allow to harvest both the record and the files. 
> You can see it here: 
> https://jira.duraspace.org/browse/DS-4028
> https://groups.google.com/d/msg/dspace-tech/95xmbswHxW0/CEPvzWVvCAAJ
>
> After thinking that the problem was related with the DSpace 6.3 OAI client 
> I downgrade my second server to DSpace 5.10 but when I create a collection 
> and begi to harvest, I get the following:
>
> 2019-01-24 16:42:45,221 INFO  org.dspace.harvest.OAIHarvester @ 
> Collections ready for immediate harvest: [1]
> 2019-01-24 16:42:45,226 INFO  org.dspace.harvest.OAIHarvester @ Thread 
> queued up: Thread[Thread-159,5,main]
> 2019-01-24 16:42:45,226 INFO  org.dspace.harvest.OAIHarvester @ Thread 
> started: Thread[Thread-160,5,main]
> 2019-01-24 16:42:45,226 INFO  org.dspace.harvest.OAIHarvester @ Thread for 
> collection 1 starts.
> 2019-01-24 16:42:45,285 INFO  org.dspace.harvest.OAIHarvester @ HTTP 
> Request: http:
> //./oai/request?verb=ListRecords=2019-01-24T19:42:45Z=col_123456789_2076=oai_dc
> 2019-01-24 16:42:45,292 INFO  org.dspace.harvest.OAIHarvester @ Found 35 
> records to process
> 2019-01-24 16:42:45,299 ERROR org.dspace.harvest.OAIHarvester @ Harvesting 
> error occurred while processing an OAI record: OAI server returned the 
> following errors during getDescMD execution: [idDoesNotExist]
> 2019-01-24 16:42:45,302 INFO  org.dspace.content.Collection @ anonymous::
> update_collection:collection_id=1
> 2019-01-24 16:42:45,304 WARN  org.dspace.core.Context @ anonymous::
> restore_auth_sys_state:not previous state info available null
> 2019-01-24 16:42:45,305 INFO  org.dspace.harvest.OAIHarvester @ Thread for 
> collection 1 completes.
> 2019-01-24 16:42:46,229 INFO  org.dspace.harvest.OAIHarvester @ Done with 
> iteration 34
>
>
> I cleared OAI cache in the main server, reimported, restarted Tomcat but 
> nothing changed. It only works when I harvest only the records.
>
> So, what else could I do?.
> Where is the problem?
> How could I have a second instance to publish only those non private 
> collections without manually export from server A and importing in server B?
>
> Thank in advance
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


[dspace-tech] Re: Filter collections by a view policy: dspace63

2019-01-31 Thread Diego Brice
Hi, please, if you receive an answer (or just find a way to do this) let me 
know because is the same feature I´m looking for!!!

TIA

El lunes, 28 de enero de 2019, 13:33:56 (UTC-3), 667...@gmail.com escribió:
>
> Hi, i need to display a list of collections that a user has been 
> explicitly given the VIEW policy: ability to view and consequently, to list 
> the collection (for example, on a community page). If a user does not have 
> this permission, a collection should be excluded from all lists (so in 
> effect, a user would not be aware of its existence)
>
> I have this working in Dspace 5.1 where getCollections() in Community.java 
> has comfortable access to the authorize manager and the context. The list 
> here is looped one more time, non-authorized collections are excluded.
> But now in Dspace 6.3 in Community.java there is neither: no authorize 
> service and no context. 
>
> I tried already redeclaring getCollection(Context context) but a) even if 
> it compiles, Tomcat does not start and b) very dirty as all calls to 
> getCollection() need to be adjusted 
>
> Another idea is to forbid direct access to community.getCollection() by 
> declaring it protected and redefine it in the CommunityService service but 
> here again: very dirty, all code around the whole Dspace will need to be 
> changed to call the service instead
>
> So my questions here would be:
> - What would be a proper solution to exclude some collections from the 
> list Community.getCollections() return?
> - Or, is there any other way to achieve the goal?
>
> Thanks!
>
> --667i
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


Re: [dspace-tech] Problems using pg_restore to populate repository db

2019-01-31 Thread Monika Mevenkamp
Kevin

You may want to reindex solo - a lot of the listing functionality (at least in 
JSPUI) rely on the sole index .

> $DSPACE_HOME/bin/dspace index-discovery -f

-f (for force)  may not be necessary - bur can’t hurt 


Monika

--—
Monika Mevenkamp 
OIT - Princeton University 
Phone: 609 258 4161 
Skype: mo-meven



> On Jan 30, 2019, at 4:07 PM, Kev Evans  wrote:
> 
> Hi,
> 
> After having problems using  AIP packages to export an entire site I am 
> rsyncing the  assetstore and using pg_dump and pg_restore.
> 
> I have restored the dump into an existing database but even though it 
> completes successfully. I see nothing new in the repository apart from the 
> initial Test community and collections and items. 
> 
> My questions are do I drop and recreate the  database and then  the 
> pg_restore the dump? Or is it as simple  as rebuilding the discovery index?
> 
> Unsure of my next step. Please help.
> 
> Kevin
> 
> -- 
> All messages to this mailing list should adhere to the DuraSpace Code of 
> Conduct: https://duraspace.org/about/policies/code-of-conduct/ 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to dspace-tech+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to dspace-tech@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


[dspace-tech] Re: Problems using pg_restore to populate repository db

2019-01-31 Thread Kev Evans
Hi Andrea 

Many thanks. I've tried that with no more success. Two things to say: 

The source DB has a different owner to the New DB 
Its a migration from Dspace 4.1 > DSpace 6.3

here is the command: 

pg_restore -h localhost -p 5432 --no-owner --role=dspace -U dspace -w  -c  
-e /usr1/home/dora/dora19dbdumps/dora11bk

I have assigned no-owner but should i define the new owner? 

Thanks for your help so far. I appreciate any more advice you can give

Cheers

Kevin


On Wednesday, 30 January 2019 21:07:10 UTC, Kev Evans wrote:
>
> Hi,
>
> After having problems using  AIP packages to export an entire site I am 
> rsyncing the  assetstore and using pg_dump and pg_restore.
>
> I have restored the dump into an existing database but even though it 
> completes successfully. I see nothing new in the repository apart from the 
> initial Test community and collections and items. 
>
> My questions are do I drop and recreate the  database and then  the 
> pg_restore the dump? Or is it as simple  as rebuilding the discovery index?
>
> Unsure of my next step. Please help.
>
> Kevin
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.