[dspace-tech] Re: Dspace Database Upgrade[from 1.6 to 6.0] ERROR: cannot drop table metadatavalue column resource_id

2016-11-22 Thread Tim GD 
Finally, I modify those two views and it can be done.

Tim GD於 2016年11月23日星期三 UTC+8上午10時45分25秒寫道：
>
> After upgraded the dsapce from 1.6.2 to 6.0(ant update) in windows, I 
> tried to upgrade the database, but it exists error in database migration.
> There is an error.
>  ERROR: cannot drop table metadatavalue column resource_id because other 
> objects depend on it
>
> When I drop the column resource_id by using cascade and migrate again, it 
> will say that the column resource_id does not exist.
> How to solve that problem? 
>
> The following are the command line(*dspace database info* & *dspace 
> database migrate*)
>
> C:\dspace\bin>dspace database info
> Using DSpace installation in: C:\dspace
>
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5433/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 9.6.0
> Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1212.jre6
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
>
>
> ++--+---
> --+-+
> | Version| Description  | 
> Installed
> on| State   |
>
> ++--+---
> --+-+
> | 1.1| Initial DSpace 1.1 database schema   |
>   | Pending |
> | 1.2| Upgrade to DSpace 1.2 schema |
>   | Pending |
> | 1.3| Upgrade to DSpace 1.3 schema |
>   | Pending |
> | 1.3.9  | Drop constraint for DSpace 1 4 schema|
>   | Pending |
> | 1.4| Upgrade to DSpace 1.4 schema |
>   | Pending |
> | 1.5| Upgrade to DSpace 1.5 schema |
>   | Pending |
> | 1.5.9  | Drop constraint for DSpace 1 6 schema|
>   | Pending |
> | 1.6| Upgrade to DSpace 1.6 schema |
>   | Pending |
> | 1.7| Upgrade to DSpace 1.7 schema |
>   | Pending |
> | 1.8| Upgrade to DSpace 1.8 schema |
>   | Pending |
> | 3.0| Upgrade to DSpace 3.x schema |
>   | Pending |
> | 4.0| Upgrade to DSpace 4.x schema |
>   | Pending |
> | 4.9.2015.10.26 | DS-2818 registry update  |
>   | Pending |
> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy  |
>   | Pending |
> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint |
>   | Pending |
> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects |
>   | Pending |
> | 5.6.2016.08.23 | DS-3097  |
>   | Pending |
> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration   |
>   | Pending |
> | 6.0.2015.03.07 | DS-2701 Hibernate migration  |
>   | Pending |
> | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration |
>   | Pending |
> | 6.0.2016.01.03 | DS-3024  |
>   | Pending |
> | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables|
>   | Pending |
> | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin  |
>   | Pending |
> | 6.0.2016.04.01 | DS-1955 Increase embargo reason  |
>   | Pending |
> | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix  |
>   | Pending |
> | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights   |
>   | Pending |
> | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column   |
>   | Pending |
> | 6.0.2016.07.21 | DS-2775  |
>   | Pending |
> | 6.0.2016.07.26 | DS-3277 fix handle assignment|
>   | Pending |
> | 6.0.2016.08.23 | DS-3097  |
>   | Pending |
>
> ++--+---
> --+-+
>  
>
> NOTE: This database is NOT yet initialized for auto-migrations (via 
> Flyway).
>
> Your database looks to be compatible with DSpace version 1.6
> All upgrades *after* version 1.6 will be run during the next migration.
>
> If you'd like to upgrade now, simply run 'dspace database migrate'.
>
> C:\dspace\bin>dspace database migrate
> Using DSpace installation in: C:\dspace
>
> Database URL: jdbc:postgresql://localhost:5433/dspace
> Migrating database to latest version... (Check dspace logs for details)
> Migration exception:
> java.sql.SQLException: Flyway migration error occurred
> at 
>

Re: [dspace-tech] DSPACE-CRIS error load publications

2016-11-22 Thread 陳彥棠 

Dear Luigi Andrea

I try to install dspace-cris-5.6.1 ,
but step " Administrator Account: Create an initial administrator account"  
has been wrong!


dspace create-administrator error message => dspace-cris-5.6.1.png

There is always an same error in this step that I install dspace-cris-5.6.1

Although dspace-cris-5.6.1 has started successfully , Administrator account 
is alway failure

but I install dspace-cris-5.5.0  step " Administrator Account: Create an 
initial administrator account"  no problem!


Installation environment

  jdk1.8.0_101
  postgresSQL 9.5
  tomcat 8.0.37   
  dspace-cris-5.6.1

Regards


Sincerly yours, Yen-Tang Chen

Pascarelli Luigi Andrea於 2016年11月21日星期一 UTC+8下午10時26分26秒寫道：
>
> I checked your web application and I think that you have many problems not 
> only this!
>
> I see that you are testing the DSpace CRIS version 5.5.0 please download 
> the last stable version 5.6.1 from https://github.com/4Science/DSpace.git 
> (https://github.com/4Science/DSpace/releases/tag/dspace-cris-5.6.1)
>
> In any case the error is related to this piece of code 
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/content/Community.java#L343
>
> Check your database maybe you fell into an installation issue. 
>
> Please open a database console and run this query:
>
> select * from metadataschemaregistry where short_id = 'dc';
>
> and this query:
>
> select * from metadatafieldregistry where metadata_schema_id = 1 and 
> element = 'title' and qualifier is null;
>
> Let me know.
>
> Best,
>
> Luigi Andrea
>
> Il 21/11/2016 13:09, Vitor Rodrigues ha scritto:
>
> Hello, 
>
> I got this error when i tried load the publications
>
> 2016-11-21 09:34:28,125 WARN  
> org.dspace.app.webui.servlet.InternalErrorServlet @ 
> :session_id=7AC3DE4A841863ADB075FC76FC3B85BA:internal_error:-- URL Was: 
> http://200.145.5.2/simple-search?query==publications
> -- Method: GET
> -- Parameters were:
> -- query: ""
> -- location: "publications"
>
> java.lang.NullPointerException
>   at org.dspace.content.Community.findAllTop(Community.java:343)
>   at 
> org.dspace.app.webui.discovery.DiscoverySearchRequestProcessor.doSimpleSearch(DiscoverySearchRequestProcessor.java:258)
>   at 
> org.dspace.app.webui.servlet.SimpleSearchServlet.doDSGet(SimpleSearchServlet.java:63)
>   at 
> org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:119)
>   at 
> org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:67)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>   at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>   at 
> org.dspace.app.webui.cris.filter.ExploreLocationFilter.doFilter(ExploreLocationFilter.java:88)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>   at 
> org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>   at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>   at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:221)
>   at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>   at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
>   at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
>   at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
>   at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:956)
>   at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>   at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
>   at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
>   at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
>   at 
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at

[dspace-tech] Dspace Database Upgrade[from 1.6 to 6.0] ERROR: cannot drop table metadatavalue column resource_id

2016-11-22 Thread Tim GD 
After upgraded the dsapce from 1.6.2 to 6.0(ant update) in windows, I tried 
to upgrade the database, but it exists error in database migration.
There is an error.
 ERROR: cannot drop table metadatavalue column resource_id because other 
objects depend on it

When I drop the column resource_id by using cascade and migrate again, it 
will say that the column resource_id does not exist.
How to solve that problem? 

The following are the command line(*dspace database info* & *dspace 
database migrate*)

C:\dspace\bin>dspace database info
Using DSpace installation in: C:\dspace

Database Type: postgres
Database URL: jdbc:postgresql://localhost:5433/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 9.6.0
Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1212.jre6
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)

++--+---
--+-+
| Version| Description  | 
Installed
on| State   |
++--+---
--+-+
| 1.1| Initial DSpace 1.1 database schema   |
  | Pending |
| 1.2| Upgrade to DSpace 1.2 schema |
  | Pending |
| 1.3| Upgrade to DSpace 1.3 schema |
  | Pending |
| 1.3.9  | Drop constraint for DSpace 1 4 schema|
  | Pending |
| 1.4| Upgrade to DSpace 1.4 schema |
  | Pending |
| 1.5| Upgrade to DSpace 1.5 schema |
  | Pending |
| 1.5.9  | Drop constraint for DSpace 1 6 schema|
  | Pending |
| 1.6| Upgrade to DSpace 1.6 schema |
  | Pending |
| 1.7| Upgrade to DSpace 1.7 schema |
  | Pending |
| 1.8| Upgrade to DSpace 1.8 schema |
  | Pending |
| 3.0| Upgrade to DSpace 3.x schema |
  | Pending |
| 4.0| Upgrade to DSpace 4.x schema |
  | Pending |
| 4.9.2015.10.26 | DS-2818 registry update  |
  | Pending |
| 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy  |
  | Pending |
| 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint |
  | Pending |
| 5.0.2014.09.26 | DS-1582 Metadata For All Objects |
  | Pending |
| 5.6.2016.08.23 | DS-3097  |
  | Pending |
| 6.0.2015.03.06 | DS 2701 Dso Uuid Migration   |
  | Pending |
| 6.0.2015.03.07 | DS-2701 Hibernate migration  |
  | Pending |
| 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration |
  | Pending |
| 6.0.2016.01.03 | DS-3024  |
  | Pending |
| 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables|
  | Pending |
| 6.0.2016.02.25 | DS-3004-slow-searching-as-admin  |
  | Pending |
| 6.0.2016.04.01 | DS-1955 Increase embargo reason  |
  | Pending |
| 6.0.2016.04.04 | DS-3086-OAI-Performance-fix  |
  | Pending |
| 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights   |
  | Pending |
| 6.0.2016.05.10 | DS-3168-fix-requestitem item id column   |
  | Pending |
| 6.0.2016.07.21 | DS-2775  |
  | Pending |
| 6.0.2016.07.26 | DS-3277 fix handle assignment|
  | Pending |
| 6.0.2016.08.23 | DS-3097  |
  | Pending |
++--+---
--+-+
 

NOTE: This database is NOT yet initialized for auto-migrations (via Flyway).

Your database looks to be compatible with DSpace version 1.6
All upgrades *after* version 1.6 will be run during the next migration.

If you'd like to upgrade now, simply run 'dspace database migrate'.

C:\dspace\bin>dspace database migrate
Using DSpace installation in: C:\dspace

Database URL: jdbc:postgresql://localhost:5433/dspace
Migrating database to latest version... (Check dspace logs for details)
Migration exception:
java.sql.SQLException: Flyway migration error occurred
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.j
ava:666)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.j
ava:574)
at 
org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:222)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at

Re: [dspace-tech] Dspace-CRIS OAI-pmh Error

2016-11-22 Thread 陳彥棠 





*Dear Bollini AndreaI try to add  this line 126  " c.turnOffItemWrapper(); 
" in the " 
C:\DSpace-dspace-cris-5.5.0\dspace-api\src\main\java\org\dspace\harvest\OAIHarvester.java
 
"but it is errors for the **mvn package  , I can not find the method " *


*turnOffItemWrapper()"...  Would i need to add those parameters?*




*Regards*


*Sincerly yours, Yen-Tang Chen*


Bollini Andrea於 2016年11月22日星期二 UTC+8下午5時28分42秒寫道：
>
> Hi 
>
> it looks as a bug in DSpace-CRIS. It should be enough to add this line
>
> c.turnOffItemWrapper();
>
> here
>
>
> https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/harvest/OAIHarvester.java#L126
>
> Unfortunately I have no time today to verify, can you run a fast test and 
> report if it solves so to include the fix in the next release?
> Thanks,
> Andrea
>
> Il 22/11/2016 04:35, 陳彥棠 ha scritto:
>
> Dear all
>
> I run Dspace-CRIS 5.5.0  OAI-pmh error 
>
> I see Dspace-CRIS Edit Collection Last Harvest Result=> Error occurred 
> while processing an OAI record
> So I checking dspace.log  message
>
> dspace.log   message
>
>  INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4179
>  INFO  org.dspace.content.WorkspaceItem @ 
> anonymous::create_workspace_item:workspace_item_id=-1item_id=4179collection_id=1
>  ERROR org.dspace.harvest.OAIHarvester @* Harvesting error occurred while 
> processing an OAI record: The 'item' schema has not been defined in this 
> DSpace instance. *
>  INFO  org.dspace.content.Collection @ 
> anonymous::update_collection:collection_id=1
>  INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 completes.
>  INFO  org.dspace.harvest.OAIHarvester @ Done with iteration 5
>  INFO  org.dspace.harvest.OAIHarvester @ Collections ready for immediate 
> harvest: [1]
>  INFO  org.dspace.harvest.OAIHarvester @ Thread queued up: 
> Thread[Thread-228,5,main]
>  INFO  org.dspace.harvest.OAIHarvester @ Thread started: 
> Thread[Thread-229,5,main]
>  INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 starts.
>  INFO  org.dspace.harvest.OAIHarvester @ HTTP Request: 
> http://ntur.lib.ntu.edu.tw/ir-oai/request?verb=ListRecords=2016-11-22T02:45:42Z=hdl_246246_43199=oai_dc
>  INFO  org.dspace.harvest.OAIHarvester @ Found 100 records to process
>  INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4180
>  INFO  org.dspace.content.Item @ anonymous::create_item:item_id=4180
>  INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4180
>  INFO  org.dspace.content.WorkspaceItem @ 
> anonymous::create_workspace_item:workspace_item_id=-1item_id=4180collection_id=1
>  ERROR org.dspace.harvest.OAIHarvester @ Harvesting error occurred while 
> processing an OAI record: The 'item' schema has not been defined in this 
> DSpace instance. 
>  INFO  org.dspace.content.Collection @ 
> anonymous::update_collection:collection_id=1
>  INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 completes.
>  WARN  org.dspace.storage.rdbms.DatabaseManager @ Already closed.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *java.sql.SQLException: Already closed. at 
> org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:114) 
> at 
> org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:191)
>  
> at 
> org.dspace.storage.rdbms.DatabaseManager.freeConnection(DatabaseManager.java:676)
>  
> at org.dspace.core.Context.abort(Context.java:567) at 
> org.dspace.core.Context.finalize(Context.java:733) at 
> java.lang.System$2.invokeFinalize(Unknown Source) at 
> java.lang.ref.Finalizer.runFinalizer(Unknown Source) at 
> java.lang.ref.Finalizer.access$100(Unknown Source) at 
> java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source) *It is my 
> database  schemas tables  item => item_id=4179 *(ps:**item_id=4179)*
> but database have obviously data . 
>
> I also tried using dspace 5.5 OAI-pmh on * same condition*
> It is a successful execution*(ps:dspace-5.5 jspui, dspace-5.5.log*
>
> *) *Why use dspace-cris oai in question?
>
>
> I'm sorry that my English is not good ...
> Description of the expression may not be clear...
>
>
> Regards
>
>
> Sincerly yours, Yen-Tang Chen
>
>
> -- 
> 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...@googlegroups.com .
> To post to this group, send email to dspac...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Andrea Bollini
> Chief Technology and Innovation Officer
>
> 4Science,  www.4science.it
> office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
>

[dspace-tech] Customizing metadata

2016-11-22 Thread Digna Rosario 
Mostrar contenido recortado
Good Morning.

I have dspace-5.1 installed and the user interface is xmlui. I am 
interested in translating and modifying the metadata label, in addition to 
changing the order of the metadata, to improve the display of the item:

dc.contributor.author
dc.title
dc.subject, entre otros.
Change it to:

Autor
Título
Tema
Could you tell me which configuration files to modify?

Best Regards,

Digna

-- 
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] Default Group for new user

2016-11-22 Thread helix84 
On Tue, Nov 22, 2016 at 6:04 PM, Donald Bynum  wrote:
> Thanks Terry.  This now leads me to an associated question.  Currently I am
> using PasswordAuthentication.  I want to get LDAP authentication working,
> but I need to do some research on which attributes we are using in our AD.
> Can I switch back and forth between Password and LDAP authentication
> protocols without doing any "damage"?

You can have both authentication options enabled at the same time,
look at authentication.cfg and the related documentation.

However, assuming you want LDAP autoregistration on, any accounts that
have logged in will have an EPerson created in DSpace. Just make sure
to map the correct attribute to netid (you can think of it as the
primary key which identifies users in DSpace). Any other attributes
can be remapped later and their values will be updated upon the next
login of that user.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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] LDAP Authentication

2016-11-22 Thread Donald Bynum 
Jeffrey,

Thanks for that.  There is a slight inconsistency in the docs (after your 
hint I went back and looked again).  The docs suggest that when theer are 
multiple auth mrthods configured that DSpace will try each method until 
success.  What I am seeing is, in fact, a list of links (one for each auth 
method) at the login screen.  I would have preferred it the way the docs 
suggested.  But, in any case, you pointed me in th eright direction to get 
back to where I needed to be.

Regards,

Don.

On Tuesday, November 22, 2016 at 2:39:07 PM UTC-5, Jeffrey Sheldon wrote:

> Don, 
>
> I would recommend enabling both LDAP and Password authentication, at least 
> long enough to log in under the older administrator account and promote any 
> accounts created through LDAP logins (or create a temporary one to feel 
> things out). 
>
> You can configure for both like so in config/modules/authentication.cfg 
>
> plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \ 
> org.dspace.authenticate.LDAPAuthentication, \ 
> org.dspace.authenticate.PasswordAuthentication 
>
>
> I had thought that the LDAP bind simply replaced auth on an existing 
> account, though I can see situations where configuration might cause 
> conflicts. 
>
> If this response misses your point, please let me know. 
>
>
> -Jeff 
>
>  
> From: dspac...@googlegroups.com   > on behalf of Donald Bynum  
> Sent: Tuesday, November 22, 2016 1:25 PM 
> To: DSpace Technical Support 
> Subject: [dspace-tech] LDAP Authentication 
>
> I have DSpace 5.5 with XMLUI and Mirage.  I initially set up DSpace with 
> Password Authentication.  I now want to switch to LDAP Authentication.  I 
> have configured the authentication config file and the ldap config file. 
>  All appears good except that I now see to have zapped my own administrator 
> account.  How can I get my DSpace account back to being an administrator 
> account?  I can revert my DSpace back to Pasword Auth and my old Admin 
> account works as an admin again.  What I need is my LDAP account to also be 
> an admin account, so that I can revert back to LDAP auth and still have 
> admin rights. 
>
> Regards, 
>
> Don. 
>
> -- 
> 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...@googlegroups.com  dspace-tech+unsubscr...@googlegroups.com >. 
> To post to this group, send email to dspac...@googlegroups.com 
> . 
> Visit this group at https://groups.google.com/group/dspace-tech. 
> For more options, visit https://groups.google.com/d/optout.

-- 
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] LDAP Authentication

2016-11-22 Thread Terry Brady 
You should be able to provide multiple authentication methods (if
appropriate).  When a user clicks login, they will be prompted for the
authentication method.

You should be able use the create-administrator command from the command
line to make your account an administrator account.

Look at the email address that was created for your LDAP account and make
it into an administrator.

Terry

On Tue, Nov 22, 2016 at 11:25 AM, Donald Bynum  wrote:

> I have DSpace 5.5 with XMLUI and Mirage.  I initially set up DSpace with
> Password Authentication.  I now want to switch to LDAP Authentication.  I
> have configured the authentication config file and the ldap config file.
> All appears good except that I now see to have zapped my own administrator
> account.  How can I get my DSpace account back to being an administrator
> account?  I can revert my DSpace back to Pasword Auth and my old Admin
> account works as an admin again.  What I need is my LDAP account to also be
> an admin account, so that I can revert back to LDAP auth and still have
> admin rights.
>
> Regards,
>
> Don.
>
> --
> 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.
>



-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
http://georgetown-university-libraries.github.io/

425-298-5498 (Seattle, WA)

-- 
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] LDAP Authentication

2016-11-22 Thread Jeffrey Sheldon 
Don,

I would recommend enabling both LDAP and Password authentication, at least long 
enough to log in under the older administrator account and promote any accounts 
created through LDAP logins (or create a temporary one to feel things out).

You can configure for both like so in config/modules/authentication.cfg

plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
org.dspace.authenticate.LDAPAuthentication, \
org.dspace.authenticate.PasswordAuthentication


I had thought that the LDAP bind simply replaced auth on an existing account, 
though I can see situations where configuration might cause conflicts.

If this response misses your point, please let me know.


-Jeff


From: dspace-tech@googlegroups.com  on behalf of 
Donald Bynum 
Sent: Tuesday, November 22, 2016 1:25 PM
To: DSpace Technical Support
Subject: [dspace-tech] LDAP Authentication

I have DSpace 5.5 with XMLUI and Mirage.  I initially set up DSpace with 
Password Authentication.  I now want to switch to LDAP Authentication.  I have 
configured the authentication config file and the ldap config file.  All 
appears good except that I now see to have zapped my own administrator account. 
 How can I get my DSpace account back to being an administrator account?  I can 
revert my DSpace back to Pasword Auth and my old Admin account works as an 
admin again.  What I need is my LDAP account to also be an admin account, so 
that I can revert back to LDAP auth and still have admin rights.

Regards,

Don.

--
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.

-- 
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] LDAP Authentication

2016-11-22 Thread Donald Bynum 
I have DSpace 5.5 with XMLUI and Mirage.  I initially set up DSpace with 
Password Authentication.  I now want to switch to LDAP Authentication.  I 
have configured the authentication config file and the ldap config file.  
All appears good except that I now see to have zapped my own administrator 
account.  How can I get my DSpace account back to being an administrator 
account?  I can revert my DSpace back to Pasword Auth and my old Admin 
account works as an admin again.  What I need is my LDAP account to also be 
an admin account, so that I can revert back to LDAP auth and still have 
admin rights.

Regards,

Don.

-- 
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] Default Group for new user

2016-11-22 Thread Donald Bynum 
Thanks Terry.  This now leads me to an associated question.  Currently I am
using PasswordAuthentication.  I want to get LDAP authentication working,
but I need to do some research on which attributes we are using in our AD.
Can I switch back and forth between Password and LDAP authentication
protocols without doing any "damage"?

Regards,

Don.

On Mon, Nov 21, 2016 at 2:27 PM, Donald Bynum  wrote:

> I am running DSpace 5.5 with XMLUI and Mirage.  Is there a way to specify
> a non-anonymous group for a new user?  I'd like all new users to go into a
> group which has READ access (i.e. able to view and download content).  The
> ultimate goal is to only allow view and download to logged in users, but I
> don't want to have to perform a "manual" admin task for each new user,
> rather have them default to a group which has READ access to the repository.
>
> Regards,
>
> Don.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/dspace-tech/ZPMoZV2PKGg/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>



-- 


Donald E. Bynum
byn...@gmail.com

-- 
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] Workflow configuration in JSPUI

2016-11-22 Thread Bollini Andrea 
Hi Lluís,

you cannot use the Configurable Reviewer Workflow with DSpace-CRIS as it is a 
XMLUI only feature.

The workflow.xml is related to such feature so you need to ignore it.

To configure the 3-step workflow with DSpace-CRIS/JSPUI you only need to edit 
the collection where you want to enable the workflow. You can create just the 
step that you need

- step1 allow you to accept / reject

- step 2 allow you to edit / accept / reject

- step 3 allow you only to edit

and assign to each step that you decide to enable the eperson that are allowed 
to perform the step.

If you need to configure the same workflow on more than one collection it could 
be convenient to manually define some groups for your reviewer (i.e "Reviewers 
step1", "Reviewers step2", etc.) and make such group a member, so a subgroup, 
of the workflow_x_step collection group.

See also the official documentation about the standard dspace workflow system:

- 
https://wiki.duraspace.org/display/DSDOC5x/Functional+Overview#FunctionalOverview-WorkflowSteps

Hope this help,
Andrea

Il 10/11/2016 14:01, Lluís Madurell Alemany ha scritto:
Been working on that, so far we have:

Error while retrieving workflow for the following collection: 
Seems that the ID is correct.

In our workflow.xml:






And then the roles and steps and so on.




-
Lluís Madurell Alemany
Lluis_tgn

2016-11-10 9:20 GMT+01:00 Lluís Madurell Alemany 
>:
Hi

We are using a Dspace 5.x with CRIS Module along with JSPUI. We are not looking 
to change to XMLUI.

We are also aware of the limitations when configuring the workflow in our 
system, having only 3 steps is fine. See: 
http://dspace.2283337.n4.nabble.com/How-to-Add-more-than-3-Workflow-Steps-tp4663012p4663067.html

Can we expect to fully configurate these 3 steps and be able to use JSPUI UI 
for the reviewers? Can we just set 2 steps? Can we change all the roles and 
steps according to our Groups/EPersons? Do we have to enable Configurable 
Reviewer Workflow obligatory (implies changes in database)?

Cheers!
--
You received this message because you are subscribed to a topic in the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/dspace-tech/GUJh-n4jeQw/unsubscribe.
To unsubscribe from this group and all its topics, 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.

--
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.


--
Andrea Bollini
Chief Technology and Innovation Officer

4Science,  www.4science.it
office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
mobile: +39 333 934 1808
skype: a.bollini
linkedin: andreabollini
orcid: -0002-9029-1854

an Itway Group Company
Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates

-- 
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] Re: vagrant-dspace install issues - librarian-puppet?

2016-11-22 Thread Hardy Pottinger 
> ==> vagrant-dspace: Unable to connect to https://forgeapi.puppetlabs.com:
end of file reached
> ==> vagrant-dspace:  (
> ==> vagrant-dspace: Faraday::ConnectionFailed
> ==> vagrant-dspace: )

I think this may be the clue I needed. I'll consult with the
librarian-puppet people on IRC and see if they have a suggestion. I know
(thanks to a tip from fellow committer Kim Shepherd) that the forge API
seems to require a user agent:
https://forgeapi.puppetlabs.com/#user-agent-required and that might be at
play here.

--Hardy

On Mon, Nov 21, 2016 at 4:07 PM, Darryn Brooking <
darryn.brook...@waikato.ac.nz> wrote:

> I'm struggling to; hence my question: where can I find more error messages?
>
> More to go on...
>
> Git for Windows - Git Bash reports version 2.8.1.windows.1
>
> I think the SSH error is a red herring - i.e. it's just how vagrant is
> communicating with the VM to run the script on the VM.
>
> In trying to get it installed, so far I've encountered the following
> issues and fixed them as follows:
>
>> cable connected:off
>>
>> Insert into Vagrantfile from line 83
>>
>># Bugfix for "Cable connected: off"
>>  config.vm.provider :virtualbox do |vm|
>>  vm.customize [
>>  "modifyvm", :id,
>>  "--cableconnected1", "on",
>>  ]
>>  end
>>
>> [edit
>> 
>> ]Too many virtual memory requests
>>
>> disable TrendMicro Antivirus
>> [edit
>> 
>> ]SSH error connecting to GitHubWindowsPer Windows hack in the
>> Vagrantfile line ~173, use Git Bash to create a github_rsa ssh keypair
>> in ~/.ssh and add the public key to your GitHub account.
>
>
> Full debug log attached.
>
> Here's the full (non-debug) log:
>
> D:\Dev\dspace\vagrant-dspace>vagrant up
> Bringing machine 'vagrant-dspace' up with 'virtualbox' provider...
> ==> vagrant-dspace: Importing base box 'box-cutter/ubuntu1604'...
> ==> vagrant-dspace: Matching MAC address for NAT networking...
> ==> vagrant-dspace: Checking if box 'box-cutter/ubuntu1604' is up to
> date...
> ==> vagrant-dspace: Setting the name of the VM: dspace-dev
> ==> vagrant-dspace: Clearing any previously set network interfaces...
> ==> vagrant-dspace: Preparing network interfaces based on configuration...
> vagrant-dspace: Adapter 1: nat
> vagrant-dspace: Adapter 2: hostonly
> ==> vagrant-dspace: Forwarding ports...
> vagrant-dspace: 8080 (guest) => 8080 (host) (adapter 1)
> vagrant-dspace: 5432 (guest) => 5432 (host) (adapter 1)
> vagrant-dspace: 22 (guest) =>  (host) (adapter 1)
> ==> vagrant-dspace: Running 'pre-boot' VM customizations...
> ==> vagrant-dspace: Booting VM...
> ==> vagrant-dspace: Waiting for machine to boot. This may take a few
> minutes...
> vagrant-dspace: SSH address: 127.0.0.1:
> vagrant-dspace: SSH username: vagrant
> vagrant-dspace: SSH auth method: private key
> vagrant-dspace:
> vagrant-dspace: Vagrant insecure key detected. Vagrant will
> automatically replace
> vagrant-dspace: this with a newly generated keypair for better
> security.
> vagrant-dspace:
> vagrant-dspace: Inserting generated public key within guest...
> vagrant-dspace: Removing insecure key from the guest if it's present...
> vagrant-dspace: Key inserted! Disconnecting and reconnecting using new
> SSH key...
> ==> vagrant-dspace: Machine booted and ready!
> ==> vagrant-dspace: Checking for guest additions in VM...
> vagrant-dspace: The guest additions on this VM do not match the
> installed version of
> vagrant-dspace: VirtualBox! In most cases this is fine, but in rare
> cases it can
> vagrant-dspace: prevent things such as shared folders from working
> properly. If you see
> vagrant-dspace: shared folder errors, please make sure the guest
> additions within the
> vagrant-dspace: virtual machine match the version of VirtualBox you
> have installed on
> vagrant-dspace: your host and reload your VM.
> vagrant-dspace:
> vagrant-dspace: Guest Additions Version: 5.1.6
> vagrant-dspace: VirtualBox Version: 5.0
> ==> vagrant-dspace: Setting hostname...
> ==> vagrant-dspace: Configuring and enabling network interfaces...
> ==> vagrant-dspace: Mounting shared folders...
> vagrant-dspace: /vagrant => D:/Dev/dspace/vagrant-dspace
> vagrant-dspace: /tmp/vagrant-puppet/manifests-
> 5058f1af8388633f609cadb75a75dc9d => D:/Dev/dspace/vagrant-dspace
> ==> vagrant-dspace: Running provisioner: shell...
> vagrant-dspace: Running: inline script
> ==> vagrant-dspace: Setting locale to UTF-8 (en_US.UTF-8)...
> ==> vagrant-dspace: Generating locales (this might take a while)...
> ==> vagrant-dspace:   en_AG.UTF-8
> ==> vagrant-dspace: ...
> ==> vagrant-dspace:  done
> ==> vagrant-dspace:   en_AU.UTF-8
> ==> vagrant-dspace:

Re: [dspace-tech] Dspace-CRIS OAI-pmh Error

2016-11-22 Thread Bollini Andrea 
Hi

it looks as a bug in DSpace-CRIS. It should be enough to add this line

c.turnOffItemWrapper();

here

https://github.com/4Science/DSpace/blob/dspace-5_x_x-cris/dspace-api/src/main/java/org/dspace/harvest/OAIHarvester.java#L126

Unfortunately I have no time today to verify, can you run a fast test and 
report if it solves so to include the fix in the next release?

Thanks,
Andrea

Il 22/11/2016 04:35, 陳彥棠 ha scritto:
Dear all

I run Dspace-CRIS 5.5.0  OAI-pmh error 

I see Dspace-CRIS Edit Collection Last Harvest Result=> Error occurred while 
processing an OAI record
So I checking dspace.log  message

dspace.log   message

 INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4179
 INFO  org.dspace.content.WorkspaceItem @ 
anonymous::create_workspace_item:workspace_item_id=-1item_id=4179collection_id=1
 ERROR org.dspace.harvest.OAIHarvester @ Harvesting error occurred while 
processing an OAI record: The 'item' schema has not been defined in this DSpace 
instance.
 INFO  org.dspace.content.Collection @ 
anonymous::update_collection:collection_id=1
 INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 completes.
 INFO  org.dspace.harvest.OAIHarvester @ Done with iteration 5
 INFO  org.dspace.harvest.OAIHarvester @ Collections ready for immediate 
harvest: [1]
 INFO  org.dspace.harvest.OAIHarvester @ Thread queued up: 
Thread[Thread-228,5,main]
 INFO  org.dspace.harvest.OAIHarvester @ Thread started: 
Thread[Thread-229,5,main]
 INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 starts.
 INFO  org.dspace.harvest.OAIHarvester @ HTTP Request: 
http://ntur.lib.ntu.edu.tw/ir-oai/request?verb=ListRecords=2016-11-22T02:45:42Z=hdl_246246_43199=oai_dc
 INFO  org.dspace.harvest.OAIHarvester @ Found 100 records to process
 INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4180
 INFO  org.dspace.content.Item @ anonymous::create_item:item_id=4180
 INFO  org.dspace.content.Item @ anonymous::update_item:item_id=4180
 INFO  org.dspace.content.WorkspaceItem @ 
anonymous::create_workspace_item:workspace_item_id=-1item_id=4180collection_id=1
 ERROR org.dspace.harvest.OAIHarvester @ Harvesting error occurred while 
processing an OAI record: The 'item' schema has not been defined in this DSpace 
instance.
 INFO  org.dspace.content.Collection @ 
anonymous::update_collection:collection_id=1
 INFO  org.dspace.harvest.OAIHarvester @ Thread for collection 1 completes.
 WARN  org.dspace.storage.rdbms.DatabaseManager @ Already closed.
java.sql.SQLException: Already closed.
at 
org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:114)
at 
org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:191)
at 
org.dspace.storage.rdbms.DatabaseManager.freeConnection(DatabaseManager.java:676)
at org.dspace.core.Context.abort(Context.java:567)
at org.dspace.core.Context.finalize(Context.java:733)
at java.lang.System$2.invokeFinalize(Unknown Source)
at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
at java.lang.ref.Finalizer.access$100(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)





It is my database  schemas tables  item => item_id=4179 (ps:item_id=4179)
but database have obviously data .

I also tried using dspace 5.5 OAI-pmh on  same condition
It is a successful execution(ps:dspace-5.5 jspui, dspace-5.5.log)

Why use dspace-cris oai in question?


I'm sorry that my English is not good ...
Description of the expression may not be clear...



Regards


Sincerly yours, Yen-Tang Chen


--
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.


--
Andrea Bollini
Chief Technology and Innovation Officer

4Science,  www.4science.it
office: Via Edoardo D'Onofrio 304, 00155 Roma, Italy
mobile: +39 333 934 1808
skype: a.bollini
linkedin: andreabollini
orcid: -0002-9029-1854

an Itway Group Company
Italy, France, Spain, Portugal, Greece, Turkey, Lebanon, Qatar, U.A.Emirates

-- 
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] change default new user group

2016-11-22 Thread Ahmed Maher 
thank you ,

On Tue, Nov 22, 2016 at 10:52 AM, helix84  wrote:

> On Tue, Nov 22, 2016 at 9:37 AM, Ahmed Maher  wrote:
> > i need to change the default user group for new registered users from
> > anonymous to another one
> > how can i do that ?
>
> Your question has been answered earlier today:
>
> http://dspace.2283337.n4.nabble.com/Default-Group-for-
> new-user-td4683874.html
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>

-- 
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] change default new user group

2016-11-22 Thread helix84 
On Tue, Nov 22, 2016 at 9:37 AM, Ahmed Maher  wrote:
> i need to change the default user group for new registered users from
> anonymous to another one
> how can i do that ?

Your question has been answered earlier today:

http://dspace.2283337.n4.nabble.com/Default-Group-for-new-user-td4683874.html


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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.