Re: [Dspace-tech] Error after install of DSpace 5.1

[Andrea Schweer]

  
  
Hi George,

On 26/03/15 10:55, George Stanley Kozak
  wrote:


  
  
  
  Yes, it has
  me stumped.  If I restore the Solr indexes and the postgres
  database back to the DSpace 4.2 versions and bring up DSpace
  4.2, everything works fine. 
  
I do shutdown
tomcat when I do the ant step.  Here are my steps, and let
me know if I have forgotten anything:
  


That all looks good so far


  

1) 
  Shutdown tomcat
2) 
  Run mvn –U clear package (I also tried
with the Mirage2 option)
3) 
  After successful build, I go to the
target/dspace-install directory and run “ant update”
  


As which user do you run ant? Same as the one that tomcat is running
as?


  

4) 
  After that is successful, I copy the
webpass over to tomcat
5) 
  Restart tomcat
6) 
  Go to view the system
The
system comes up and I have access to the database records,
but all browses and searches generate the index lock error.

  


When you look for the write locks after step 5, what are their
permissions? You should be able to find them (assuming a Linux
system) using
find [dspace]/solr -name "*.lock"

cheers,
Andrea


-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
  


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Error after install of DSpace 5.1

[George Stanley Kozak]

Andrea:

Yes, it has me stumped.  If I restore the Solr indexes and the postgres 
database back to the DSpace 4.2 versions and bring up DSpace 4.2, everything 
works fine.
I do shutdown tomcat when I do the ant step.  Here are my steps, and let me 
know if I have forgotten anything:

1)  Shutdown tomcat

2)  Run mvn -U clear package (I also tried with the Mirage2 option)

3)  After successful build, I go to the target/dspace-install directory and 
run "ant update"

4)  After that is successful, I copy the webpass over to tomcat

5)  Restart tomcat

6)  Go to view the system

The system comes up and I have access to the database records, but all browses 
and searches generate the index lock error.
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924


From: Andrea Schweer [mailto:schw...@waikato.ac.nz]
Sent: Wednesday, March 25, 2015 5:03 PM
To: George Stanley Kozak; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Error after install of DSpace 5.1

Hi George,
On 26/03/15 03:42, George Stanley Kozak wrote:
So, I double checked the permissions on my solr index and tomcat.  They are 
both owned by the DSpace user.  If I bring my system up in DSpace 4.2 (after a 
restore), I have no problems.  If I bring it up in 5.1, I get the error:
"SolrCore 'search' is not available due to init failure: Index locked for write 
for core search,trace=org.apache.solr.common.SolrException: SolrCore 'search' 
is not available due to init failure: Index locked for write for core search"
I can't even do an re-index.
I have to say that I'm kind of stumped here.  Works OK in 4.2, doesn't work in 
5.1

How odd. Are you running the ant step (with the 5.1 code) as the same user as 
tomcat? Also, when you run ant for the first time using the 5.1 code, tomcat 
must not be running -- ant will upgrade the solr indexes to the version used in 
DSpace 5.1 and it needs to have exclusive access to the index while that runs 
(and the mechanism for that is the write lock, which makes me suspect it's 
involved in the problem you're seeing).

You have presumably checked already that the ant step with the 5.1 code doesn't 
throw any errors.

cheers,
Andrea



--

Dr Andrea Schweer

IRR Technical Specialist, ITS Information Systems

The University of Waikato, Hamilton, New Zealand
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Embargo problems DSpace 4.0

[Andrea Schweer]

  
  
Hi Antony,

On 26/03/15 05:24, Antony Corfield [awc] wrote:

  
  I've configured DSpace 4.0 to use simple
embargo functionality including submission forms and
  dspace.cfg below. Although the embargo is lifted on the correct
  date and seems to be working fine I can't see
  the dc.rights.embargoreason and dc.rights.embargodate in the full
  item metadata view or in the database. I can see the date in the
  policies for the item (attached).
  
  
  It seems that the reason and date aren't being copied to
these metadata fields. Prior to upgrade (from 1.8) this was
working and any items that were embargoed prior to upgrade do
have these metadata fields in the full item view and in the
database.
  
  
  Any help would be very much appreciated as we really need
embargo details in the item metadata.


The simple embargo functionality doesn't use item metadata at all.
All information is stored in the policies. So the behaviour you're
asking for doesn't exist in that mechanism. The settings you quote
in your e-mail don't apply when you use the simple embargo
functionality.

If having the embargo information in the policies is not sufficient
for your needs, your best bet is probably to add fields for the
embargo date and reason to input-forms.xml, possibly on a new page
if you want to keep them separated from the other item metadata.

cheers,
Andrea


   Embargo Settings 
  
  # DC metadata field to hold the user-supplied embargo terms
  #embargo.field.terms = SCHEMA.ELEMENT.QUALIFIER
  #awc
  embargo.field.terms = dc.rights.embargoreason
  
  
  # DC metadata field to hold computed "lift date" of embargo
  embargo.field.lift = dc.rights.embargodate
  
  
  # string in terms field to indicate indefinite embargo
  embargo.terms.open = forever
  
  
  # implementation of embargo setter plugin - replace with
local implementation if applicable
  plugin.single.org.dspace.embargo.EmbargoSetter =
org.dspace.embargo.DefaultEmbargoSetter
  
  
  # implementation of embargo lifter plugin - - replace with
local implementation if applicable
  plugin.single.org.dspace.embargo.EmbargoLifter =
org.dspace.embargo.DefaultEmbargoLifter



-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
  


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Error after install of DSpace 5.1

[Andrea Schweer]

  
  
Hi George,

On 26/03/15 03:42, George Stanley Kozak
  wrote:


  
  
  
  So, I double
  checked the permissions on my solr index and tomcat.  They are
  both owned by the DSpace user.  If I bring my system up in
  DSpace 4.2 (after a restore), I have no problems.  If I bring
  it up in 5.1, I get the error: 
“SolrCore
'search' is not available due to init failure: Index locked
for write for core
search,trace=org.apache.solr.common.SolrException: SolrCore
'search' is not available due to init failure: Index locked
for write for core search”
I can’t even do
an re-index.
I have to say
that I’m kind of stumped here.  Works OK in 4.2, doesn’t
work in 5.1
  


How odd. Are you running the ant step (with the 5.1 code) as the
same user as tomcat? Also, when you run ant for the first time using
the 5.1 code, tomcat must not be running -- ant will upgrade
the solr indexes to the version used in DSpace 5.1 and it needs to
have exclusive access to the index while that runs (and the
mechanism for that is the write lock, which makes me suspect it's
involved in the problem you're seeing).

You have presumably checked already that the ant step with the 5.1
code doesn't throw any errors.

cheers,
Andrea

-- 
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
  


--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] Embargo problems DSpace 4.0

[Antony Corfield [awc]]

Hi,
I've configured DSpace 4.0 to use simple embargo 
functionality
 including submission forms and dspace.cfg below. Although the embargo is 
lifted on the correct date and seems to be working fine I can't see the 
dc.rights.embargoreason and dc.rights.embargodate in the full item metadata 
view or in the database. I can see the date in the policies for the item 
(attached).

It seems that the reason and date aren't being copied to these metadata fields. 
Prior to upgrade (from 1.8) this was working and any items that were embargoed 
prior to upgrade do have these metadata fields in the full item view and in the 
database.

Any help would be very much appreciated as we really need embargo details in 
the item metadata.

Thanks,
Antony



 Embargo Settings 
# DC metadata field to hold the user-supplied embargo terms
#embargo.field.terms = SCHEMA.ELEMENT.QUALIFIER
#awc
embargo.field.terms = dc.rights.embargoreason

# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = dc.rights.embargodate

# string in terms field to indicate indefinite embargo
embargo.terms.open = forever

# implementation of embargo setter plugin - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoSetter = 
org.dspace.embargo.DefaultEmbargoSetter

# implementation of embargo lifter plugin - - replace with local implementation 
if applicable
plugin.single.org.dspace.embargo.EmbargoLifter = 
org.dspace.embargo.DefaultEmbargoLifter


[cid:E2085C02-1B82-4E53-B80B-502BED23714B@aber.ac.uk]

Antony Corfield

Swyddog Cronfa Ddata Monitro Ymchwil / Research Monitoring Database Officer
Ymchwil, Busnes ac Arloesi / Research, Business & Innovation

Prifysgol Aberystwyth / Aberystwyth University
Llyfrgell Hugh Owen / Hugh Owen Library
Campws Penglais / Penglais Campus
Aberystwyth
Ceredigion  SY23 3DZ

Ffôn / Tel: 01970 628724
E-bost / Email: a...@aber.ac.uk
www.aber.ac.uk/rbi




--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Browse and Search & Handle-Server

[Naveen Srinivasan]

Hi Monika,

Thanks for the suggestions. I am able to run the index-discovery command
without any issues as of now .As data is huge .Its running for more than an
hour and still running. I can see the log is updated too in the log folder
which is increasing steadily.

dspace.cfg  looks good and those changes were already taken care. I hope
after index-discovery it should work .But I have question on Handle-Server
; Do we need to register our service in
http://www.handle.net/service_agreement.html ? Thanks

Regards,
Naveen
Illinois Institute of Technology
Graduate (MCS)
Mob : (312) 774-1687

On Tue, Mar 24, 2015 at 9:20 AM, Monika C. Mevenkamp 
wrote:

>
>   index-discovery is the command that  creates and updates the solr index
>
>
>  Your solr server is up iff you do not get any exceptions when running
> this command.
>
>  To fully build the index run the command with the options   -b -s
>
>  You should also have a look at your solr server.  Find instructions on
> the DSPACE wiki about how to get access from your locally running browser :
> https://wiki.duraspace.org/display/DSPACE/Solr.
>
>  Choose the ‘search’ index in the drop down on the left and have a look
> whether there is anything in the index .
>
>  make sure you do have discovery enabled in your dspace.cfg file
>  event.dispatcher.default.consumers = versioning, discovery, eperson,
> harvester
> or even more authoritatively run the command
> /bin/dspace dsprop -property
> event.dispatcher.default.consumers
>
>
>  Monika
>
>
>
>
>
>  
>  Monika Mevenkamp
> phone: 609-258-4161
> Lewis Library,Washington Road and Ivy Lane, Princeton University,
> Princeton, NJ 08544
>
>
>  On Mar 23, 2015, at 1:52 PM, Naveen Srinivasan 
> wrote:
>
>  Hi Team
>
>  I have installed Dspace 5.1 version and copied Asset Store and themes to
> the new server from old server.Site is up and everything looks good except
> couple of items.
>
>  *  Browse and Search index is not working ,When i search I get  :"Sorry,
> there are no results for this browse."
>
>  * Similarly when i use Item submission/ upload ,I am getting blank page
> after selecting any collection.
>
>  Is this because of Handle-Server ? I did not register the handle-server
> yet. Please suggest me how to fix the issue.
>
>  I ran few commands ,
>   - index-db-browse: General browse index command (requires extra
> parameters)
>  - index-discovery: Update Discovery Solr Search Index
>  - index-lucene-init: Initialise the Lucene search and browse indexes
>  - index-lucene-update: Update the Lucene search and browse indexes
>
>  These commands didn't help me to fix the issue. Thanks
>
>  Regards,
>   Naveen
> Illinois Institute of Technology
>  Graduate (MCS)
>  Mob : (312) 774-1687
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now.
> http://goparallel.sourceforge.net/___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Dspace-tech] PARTICIPATE: DuraSpace Board-Member-at-Large Elections

[Valorie Hollister]

Apologies for the cross-posting

March 24, 2015

Read it online: http://duraspace.org/node/2508 
Contact: Valorie Hollister 


Dear DSpace Community, 

As a part of the new governance model, DuraSpace is officially launching the 
nominations phase of our Board-Member-at-Large elections.

The DuraSpace Board of Directors plays a key role in setting the strategic 
direction and priorities of the DuraSpace non-profit organization. Up to this 
point all new board members  have been nominated and elected by the sitting 
board members. Along with the transition to a membership-based organization, 
there will be one (1) community elected DuraSpace board member, called the 
Board-Member-at-Large, who will be nominated by the community and elected by 
DuraSpace Members.

DuraSpace Organization Board of Directors Role
The Board of Directors works with the DuraSpace CEO, Debra Hanken Kurtz, 
helping to set the strategic direction and priorities of the DuraSpace 
non-profit organization. The responsibilities include:
Determining the organization's mission and purposes
Hiring and on-going support of the Chief Executive Officer 
Building strategic relationships, including making connections to potential 
supporters, funders, customers, stakeholders; enable the building of alliances, 
partnerships, and business relationships
Fiscal oversight and risk management, including review and approval of 
corporate financial reports and high-level decision making to ensure the fiscal 
health of the organization
Review and approval business strategies, revenue-generating, and fund raising 
strategies
Monitoring the organization's programs and services
Enhancing the organization's public image
Board members serve for a term of 2 years. The next term begins July 1, 2015 
and ends June 30, 2017. There are 4 meetings a year, 2 in-person meetings (can 
call in) and 2 conference call meetings. 

Board-Member-at-Large Nomination
Beginning today, we invite anyone in the community, DuraSpace members or 
non-member, to nominate an individual who you believe would be a good 
representative of the community.  All nominees must be from DuraSpace member 
organizations (see full list here: http://bit.ly/duraspace_members 
). Board-Member-at-Large candidates should be 
at the senior management level at their organizations, and have fiscal and 
staffing responsibility.  And of course, they will, in your judgment, be able 
to bring the commitment, creativity, and dedication that the role calls for. 
Self-nominations are welcome and you may submit more than one nomination. 
Please submit your nomination/s using this form http://bit.ly/bod_nominate 
 by April 3, 2015. 

Next Steps
At the end of the nomination process individuals nominated will be asked to 
confirm their interest in serving and to submit a brief personal statement. The 
election will take place in April, with each Member organization’s Community 
Liaison casting a vote based on the direction of their management. We will send 
additional instructions at the start of the election period.

If you have any questions about the Board-Member-at-Large nomination and 
election process please contact Valorie Hollister at vhollis...@duraspace.org. 

Valorie Hollister
Director of Membership and Finance
DuraSpace
vhollis...@duraspace.org






















--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] upgrade to dspace 5 - metadata missing ?

[Monika C. Mevenkamp]

I answered my own question -  and just in case anybody is interested 

The database upgrade in 
sqlmigration/oracle/V5.0_2014.09.26__DS-1582_Metadata_For_All_Objects.sql
had not fully executed so that properties formerly stored in various table 
(bitstream, groups, ..) had not been moved into the metadatavalues tables. 

Once I ran the relevant sql commands life started to improve 

Monika



Monika Mevenkamp
phone: 609-258-4161
Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ 
08544


> On Mar 16, 2015, at 5:42 PM, Monika C. Mevenkamp  
> wrote:
> 
> resending -my last message appears to have gone out without is message body 
> 
> 
> 
> DSPACE 5 now does a lot more with metadata. After the upgrade I see that 
> there are two new schemes: 
> 
> SELECT * FROM METADATASCHEMAREGISTRY; 
> 
>   METADATA_SCHEMA_ID   NAMESPACE   SHORT_ID   
>
>1   http://dublincore.org/documents/dcmi-terms/ dc
>2   http://www.princeton.edu/   pu
>21  http://purl.org/dc/terms/   dcterms
>22  http://dspace.org/eperson   eperson 
> 
> There are a good number of related fields for the new schemas: 
> 
> SELECT  MF.* FROM METADATAFIELDREGISTRY MF WHERE MF.METADATA_SCHEMA_ID  > 2;
> 
>   METADATA_FIELD_ID  METADATA_SCHEMA_ID  ELEMENT
>   243 21  abstract
>   244 21  accessRights
>   245 21  accrualMethod
>   ...
>   ... 
>   296 21  type
>   297 21  valid
>   298 22  firstname
>   299 22  lastname
>   300 22  phone
>   301 22  language
> 
> 
> But when I look into the metadata value table there is not a single related  
> value 
> 
> SELECT * FROM METADATAVALUE MV WHERE   MV.METADATA_FIELD_ID in 
>(SELECT  MF.METADATA_FIELD_ID FROM METADATAFIELDREGISTRY MF WHERE 
> MF.METADATA_SCHEMA_ID  > 2);
> no rows selected
> 
> 
> This does not feel right - is there a step I overlooked ?  
> I sent a question earlier in about version 5 not recognizing an IP group  - 
> see enclosed message below. I suspect that this may be a related issue.
> 
> Monika
> 
> 
> Monika Mevenkamp
> phone: 609-258-4161
> Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, 
> NJ 08544
> 
> 
>> On Mar 10, 2015, at 4:09 PM, Monika C. Mevenkamp 
>>  wrote:
>> 
>> I am upgrading to dspace 5 from 1.8 
>> 
>> I have ip authentication enabled but the system does not recognize the ip 
>> group 
>> It looks in the metadata table with 
>> 
>> 
>> DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query "select * 
>> from epersongroup e LEFT JOIN metadatavalue m on (m.resource_id = 
>> e.eperson_group_id and m.resource_type_id = ? and m.metadata_field_id = ?) 
>> where  dbms_lob.substr(m.text_value) = ?"  with parameters: 
>> 6,64,Princeton_IPs
>> 
>> Looking into my database I see that there is not a single  metadatvalue for 
>> resource type 6. 
>> I am fairly convinced I could ‘fix’ this by copying values from the 
>> EPERSONGROUP table to the metadata value table. Is that what I should do ? 
>> Does anybody have a handy UPDATE SQL statement ready to go  ? 
>> 
>> Monika
>> 
>> 
>> 
>> 
>> Monika Mevenkamp
>> phone: 609-258-4161
>> Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, 
>> NJ 08544
> 
> Monika Mevenkamp
> phone: 609-258-4161
> Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, 
> NJ 08544
> 
> 
>> On Mar 16, 2015, at 5:36 PM, Monika C. Mevenkamp  
>> wrote:
>> 
> 
> --
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette: 
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and joi

Re: [Dspace-tech] Error after install of DSpace 5.1

[George Stanley Kozak]

Hello, Andrea (and everyone else):

So, I double checked the permissions on my solr index and tomcat.  They are 
both owned by the DSpace user.  If I bring my system up in DSpace 4.2 (after a 
restore), I have no problems.  If I bring it up in 5.1, I get the error:
"SolrCore 'search' is not available due to init failure: Index locked for write 
for core search,trace=org.apache.solr.common.SolrException: SolrCore 'search' 
is not available due to init failure: Index locked for write for core search"
I can't even do an re-index.
I have to say that I'm kind of stumped here.  Works OK in 4.2, doesn't work in 
5.1

George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924


From: Andrea Schweer [mailto:schw...@waikato.ac.nz]
Sent: Tuesday, March 24, 2015 5:26 PM
To: George Stanley Kozak; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Error after install of DSpace 5.1

Hi George,
On 25/03/15 10:06, George Stanley Kozak wrote:
Thank you for your suggestions.  I did check and my tomcat (tomcat 7) is owned 
by my dspace user as is my solr index, so tomcat should be able to write to the 
solr directory (it works OK for 4.2).  So, I am not sure what is causing the 
permission problem, but I will keep checking.

Have you run a chown with the -c flag on your solr directory? That will tell 
you about any changes it makes. Might be worth it just so you can go from 
"tomcat should be able to write to the solr directory" to "tomcat is definitely 
able to write to the solr directory". Just on the off-chance this is happening 
to you: I've had nasty surprises when the solr directory was on a different 
partition and symlinked into [dspace], chown -R didn't work across the symlink 
(it changed ownership of the symlink but not of the symlinked directory).

Also, if the permissions have been wrong in the past at some point, sometimes 
the write.lock file sticks around with wrong write permissions. In that case, 
it helps to stop tomcat, delete the write.lock file, then start tomcat.

cheers,
Andrea



--

Dr Andrea Schweer

IRR Technical Specialist, ITS Information Systems

The University of Waikato, Hamilton, New Zealand
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] DSpace Upgrade from v3.1 to v5.1

[helix84]

On Thu, Mar 19, 2015 at 8:30 PM, Chelsea Lobdell
 wrote:
> Thanks Tim! I have been able to successfully run ant build. I am still not
> through the upgrade process and today I am seeing a 503 when I try to go to
> the development site with a message that reads:
> Service Temporarily Unavailable
>
> The server is temporarily unable to service your request due to maintenance
> downtime or capacity problems. Please try again later.

Hi Chelsea,

this is an error you get when you're running with HTTPD as a frontend
talking to Tomcat using AJP and the AJP connection is unavailable.
That typically happens while you restart Tomcat. If Tomcat is running
(verify using an HTTP connector, this runs on port 8080 by default)
and you still see the message even after restarting HTTPD, investigate
what's wrong with your AJP connection. Perhaps you forgot to add the
AJP connector in Tomcat's server.xml?


Regards,
~~helix84

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

--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] Question

[Peter Dietz]

Hi Luis,

Author profiles are not part of the out-of-the-box feature set of DSpace.
We are considering this feature for a future release of DSpace. In addition
to the Author Profiles that DSpace-CRIS would give you, that Andrea
mentioned, another implementation is:
https://github.com/DSpace/DSpace/pull/668

Keep in mind that an un-merged pull request is not considered an official
add-on, thus there won't be any support on it.


Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Tue, Mar 24, 2015 at 6:00 AM, Andrea Bollini  wrote:

>  Hi,
> there is an extension of DSpace named DSpace-CRIS that extends the dspace
> data model to other entities including but not limited to the researcher
> profile.
> You are able to create an expert directory, use these information during
> the submission to properly recognize author in publication and much more.
> All the additional entities play nicely with all the dissemination feature
> of dspace as the discovery search and browse system.
> Please take a look to the project website
> http://cineca.github.io/dspace-cris/
> technical documentation:
> http://cineca.github.io/dspace-cris/doc/technical-documentation.pdf
>
> and the Hong Kong University installation, currently the big DSpace-CRIS
> installation and the initial funder of the project.
> home page: http://hub.hku.hk
> a research profile: http://hub.hku.hk/cris/rp/rp00056
>
> Best regards,
> Andrea
>
> Il 23/03/2015 17.32, Luis Rojas C. (CATIE) ha scritto:
>
>  Dear Friends, in dspace exist Author profile module to install?
>
>
>
> Thanks for your support
>
>
>
>
>
> *Magister Luis Alfonso Rojas Calderón Analista/Desarollador de Sistemas
> Biblioteca Conmemorativa Orton IICA/CATIE*
>
> *Cartago, Turrialba, Turrialba*
>
>
> *30501 Costa Rica **luisro...@catie.ac.cr *
>
> *Teléfono: (506)25582439*
>
> *Fax: (506)2556-0757*
>
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
>
>
>
> ___
> DSpace-tech mailing 
> listDSpace-tech@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette: 
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
> --
> Andrea Bollini
> Soluzioni per la Ricerca Istituzionale
> Cineca
>
> Via dei Tizii, 6
> 00185 Roma, Italy
> tel. +39 06 44 486 087 - mob. +39 348 82 77 525http://www.cineca.it
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Re: [Dspace-tech] DSpace Upgrade from v3.1 to v5.1

[Tim Donohue]

Hi Chelsea,

More information on which logs to check for possible issues is on our 
Troubleshooting page on the wiki:

https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error

Some of these logs (e.g. Tomcat logs) may be in different locations 
depending on your server's setup.

Good luck,

Tim

On 3/19/2015 2:30 PM, Chelsea Lobdell wrote:
> Thanks Tim! I have been able to successfully run ant build. I am still
> not through the upgrade process and today I am seeing a 503 when I try
> to go to the development site with a message that reads:
> Service Temporarily Unavailable
>
> The server is temporarily unable to service your request due to
> maintenance downtime or capacity problems. Please try again later.
>
>
> I have checked the status of apache, postgres, and tomcat and they are
> all running.
>
> When I check the status of the handle server, it is not running. I start
> it and it returns success, but still when I check the status it is not
> running. Can you point me in the direction of what logs to start looking
> in to debug this error?
>
>
> - Chelsea
>
>
> /---/
> /Chelsea Lobdell/
> /Library Applications Programmer / Swarthmore College/
> /clobd...@swarthmore.edu / (610)690-6818/
>
> 
> *From: *"Tim Donohue" 
> *To: *"Chelsea Lobdell" 
> *Cc: *dspace-tech@lists.sourceforge.net
> *Sent: *Friday, March 13, 2015 4:35:24 PM
> *Subject: *Re: [Dspace-tech] DSpace Upgrade from v3.1 to v5.1
>
> Assuming your tomcat user can read this directory:
> /usr/local/src/dspace-5.1-src-release/dspace/target/dspace-installer/
> AND also write to "/var/dspace", then yes, running "ant update" as the
> tomcat user should work properly.
>
> Essentially, that "ant update" command needs to be able to *read* from
> the [dspace-src]/dspace/target/dspace-installer/ folder, and *write* to
> your [dspace.dir] (as configured in dspace.cfg).  So, based on that, it
> needs to be run as a user who has both of those access rights.
>
> Hopefully that helps!
>
> - Tim
>
> On 3/13/2015 2:17 PM, Chelsea Lobdell wrote:
>  > Hi Tim,
>  >
>  > Our setup is such that all dspace files are owned by tomcat and group
>  > owned by a group called tomcat. I belong to the tomcat group. Should the
>  > update be run as the tomcat user? Or should I be able to run it under my
>  > own username? Or should I try running it as root?
>  >
>  > Thank,
>  > Chelsea
>  >
>  >
>  > /---/
>  > /Chelsea Lobdell/
>  > /Library Applications Programmer / Swarthmore College/
>  > /clobd...@swarthmore.edu / (610)690-6818/
>  >
>  > 
>  > *From: *"Tim Donohue" 
>  > *To: *"Chelsea Lobdell" 
>  > *Cc: *dspace-tech@lists.sourceforge.net
>  > *Sent: *Friday, March 13, 2015 3:04:08 PM
>  > *Subject: *Re: [Dspace-tech] DSpace Upgrade from v3.1 to v5.1
>  >
>  > Hi Chelsea,
>  >
>  > This sounds like a possible file permissions issue. It sounds like the
>  > user which is running "ant update" may not have access to create
>  > files/directories under your "/var/dspace/solr/" directory.
>  >
>  > So, you may want to check the permissions on "/var/dspace/" (and
>  > everything under that), to see if your user account has proper access
>  > rights to read/write files.
>  >
>  > - Tim
>  >
>  >
>  > On 3/13/2015 1:38 PM, Chelsea Lobdell wrote:
>  >  > Hi,
>  >  >
>  >  > I've gotten to step 6 (Update Dspace Installation**) of the upgrade
>  >  > process and my build failed. Here is the output I saw:
>  >  >
>  >  > BUILD FAILED
>  >  >
>  >
> /usr/local/src/dspace-5.1-src-release/dspace/target/dspace-installer/build.xml:371:
>  >  > Failed to copy
>  >  >
>  >
> /usr/local/src/dspace-5.1-src-release/dspace/target/dspace-installer/solr-config-temp/authority/conf/admin-extra.html
>  >  > to /var/dspace/solr/authority/conf/admin-extra.html due to failed to
>  >  > create the parent directory for
>  >  > /var/dspace/solr/authority/conf/admin-extra.html
>  >  >
>  >  > Does this mean I need to manually upgrade the solr indexes? Or can I
>  >  > just copy of the file that failed to copy? Forgive me if this is a
>  >  > simple question, I am new to supporting this application.
>  >  >
>  >  > Thanks,
>  >  > Chelsea
>  >  >
>  >  >
>  >  > /---/
>  >  > /Chelsea Lobdell/
>  >  > /Library Applications Programmer / Swarthmore College/
>  >  > /clobd...@swarthmore.edu / (610)690-6818/
>  >  >
>  >  >
> 
>  >  > *From: *"Tim Donohue" 
>  >  > *To: *"Chelsea Lobdell" ,
>  >  > dspace-tech@lists.sourceforge.net
>  >  > *Sent: *Monday, March 9, 2015 2:44:51 PM
>  >  > *Subject: *Re: [Dspace-tech] DSpace Upgrade from v3.1 to v5.1
>  >  >
>  >  > Chelsea,
>  >  >
>  >  > Correct, you can upgrade directly from 3.x to 5.x per the DSpace 5
>  >  > upgrade instructions:
>  >  > https://wiki.duraspace.org/display/DSDOC5x/Upgrading+DSpace

[Dspace-tech] DSpace 4.2 navigation

[Layale Bassil]

Hello All,

I am using Dspace 4.2 and I would like to customize the right navigation where 
I want to edit the "My Account" section and remove the "Register" link. Which 
file do I  have to edit and where can I find it if I am using the Mirage theme?

One more thing, if I want to edit the item full view and remove the third 
column of the table that lists the dc fields and their values, how can I edit 
it? (this column will only show en_US and I want to remove it or hide it).

Your help is very much appreciated.

Regards.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette