Re: [Dspace-tech] ERROR: creating index discovery‏

2015-02-04 Thread euler
Hello,

If you want the dc.contributor.tutor to be authority controlled, add this
lines to your dspace.cfg:

choices.plugin.dc.contributor.tutor= LCNameAuthority
choices.presentation.dc.contributor.tutor= lookup
authority.controlled.dc.contributor.tutor= true

I don't know if using wildcards will work (eg. dc.contributor.*) as I
haven't tried it. I hope someone from the list who is also using the same
dspace version as yours can better help you.

Best of luck,

euler

 



--
View this message in context: 
http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676488.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

--
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: creating index discovery‏

2015-01-23 Thread . .
Hi Euler, thanks for your response.

 I tried what you told me. In my case, with version 4.2, I have these lines in 
my dspace.cfg file.

#  Authority Control Settings  #

plugin.named.org.dspace.content.authority.ChoiceAuthority = \
 org.dspace.content.authority.SampleAuthority = Sample, \
 org.dspace.content.authority.LCNameAuthority = LCNameAuthority, \
 org.dspace.content.authority.SHERPARoMEOPublisher = SRPublisher, \
 org.dspace.content.authority.SHERPARoMEOJournalTitle = SRJournalTitle

 I have restored the tomcat, but to run 'dspace index-discovery -f' I will get 
the same error.

 Are there any other ideas?

 Date: Thu, 22 Jan 2015 06:24:08 -0800
 From: esne...@seafdec.org.ph
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] ERROR: creating index discovery‏
 
 Hello alsapama,
 
 Please try to enable the authority plugin for dc.contributor.author. In your
 dspace.cfg, uncomment these lines (remove the #):
 
 plugin.named.org.dspace.content.authority.ChoiceAuthority = \
 org.dspace.content.authority.LCNameAuthority = LCNameAuthority, \
 choices.plugin.dc.contributor.author =  LCNameAuthority
 choices.presentation.dc.contributor.author = lookup
 authority.controlled.dc.contributor.author = true
 
 Save your dspace.cfg and restart your tomcat server.
 
 Regards,
 euler
 
 
 
 --
 View this message in context: 
 http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676317.html
 Sent from the DSpace - Tech mailing list archive at Nabble.com.
 
 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 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
  --
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
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: creating index discovery‏

2015-01-23 Thread euler
Sorry, I forgot to mention that you also have to uncomment this line in order
for the LCNameAuthority to work:

lcname.url = http://alcme.oclc.org/srw/search/lcnaf

As usual, save dspace.cfg and restart tomcat.

Regards,
euler



--
View this message in context: 
http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676346.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
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: creating index discovery‏

2015-01-23 Thread euler
Did you uncomment these lines?

choices.plugin.dc.contributor.author = LCNameAuthority
choices.presentation.dc.contributor.author = lookup
authority.controlled.dc.contributor.author = true

In dspace 4x, these lines are located here: 
https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/config/dspace.cfg#L1545-1547
https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/config/dspace.cfg#L1545-1547
  

Please note that in order to reflect these changes, you have to save first
your dspace.cfg and restart your tomcat. Also note that LCNameAuthority is
just a demo plugin for authority control for authors. I suggest upgrading to
dspace 5 and try to use  ORCID integration
https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration  .

Hope this would help you.

Regards,
euler



--
View this message in context: 
http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676340.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
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: creating index discovery‏

2015-01-23 Thread . .
Hi euler, Thanks again. For political reasons, now is not possible to upgrade 
to version 5

 I tried what you told me, but now I get this error:

  ERROR org.dspace.discovery.SolrServiceImpl DSpace @ Missing configuration 
keys for lcName Query
 java.lang.IllegalStateException: Missing DSpace configuration keys for lcName 
Query
 at org.dspace.content.authority.LCNameAuthority. init 
(LCNameAuthority.java:80)
 at sun.reflect.GeneratedConstructorAccessor14.newInstance (Unknown 
Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (Unknown 
Source)
 at java.lang.reflect.Constructor.newInstance (Unknown Source)
 at java.lang.Class.newInstance (Unknown Source)
 at org.dspace.core.PluginManager.getNamedPlugin 
(PluginManager.java:434)
 at org.dspace.core.PluginManager.getNamedPlugin 
(PluginManager.java:395)
 at org.dspace.content.authority.ChoiceAuthorityManager. init 
(ChoiceAuthorityManager.java:81)
 at org.dspace.content.authority.ChoiceAuthorityManager.getManager 
(ChoiceAuthorityManager.java:125)
 at org.dspace.browse.SolrBrowseCreateDAO.additionalIndex 
(SolrBrowseCreateDAO.java:219)
 at org.dspace.discovery.SolrServiceImpl.buildDocument 
(SolrServiceImpl.java:1393)
 at org.dspace.discovery.SolrServiceImpl.indexContent 
(SolrServiceImpl.java:215)
 at org.dspace.discovery.SolrServiceImpl.updateIndex 
(SolrServiceImpl.java:387)
 at org.dspace.discovery.IndexClient.main (IndexClient.java:127)
 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke (Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke (Unknown Source)
 at java.lang.reflect.Method.invoke (Unknown Source)
 at org.dspace.app.launcher.ScriptLauncher.runOneCommand 
(ScriptLauncher.java:225)
 at org.dspace.app.launcher.ScriptLauncher.main (ScriptLauncher.java:77)


 Any ideas?

 Date: Fri, 23 Jan 2015 02:01:39 -0800
 From: esne...@seafdec.org.ph
 To: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] ERROR: creating index discovery‏
 
 Did you uncomment these lines?
 
 choices.plugin.dc.contributor.author = LCNameAuthority
 choices.presentation.dc.contributor.author = lookup
 authority.controlled.dc.contributor.author = true
 
 In dspace 4x, these lines are located here: 
 https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/config/dspace.cfg#L1545-1547
 https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace/config/dspace.cfg#L1545-1547
   
 
 Please note that in order to reflect these changes, you have to save first
 your dspace.cfg and restart your tomcat. Also note that LCNameAuthority is
 just a demo plugin for authority control for authors. I suggest upgrading to
 dspace 5 and try to use  ORCID integration
 https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration  .
 
 Hope this would help you.
 
 Regards,
 euler
 
 
 
 --
 View this message in context: 
 http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676340.html
 Sent from the DSpace - Tech mailing list archive at Nabble.com.
 
 --
 New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
 GigeNET is offering a free month of service with a new server in Ashburn.
 Choose from 2 high performing configs, both with 100TB of bandwidth.
 Higher redundancy.Lower latency.Increased capacity.Completely compliant.
 http://p.sf.net/sfu/gigenet
 ___
 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
  --
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
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: creating index discovery‏

2015-01-22 Thread euler
Hello alsapama,

Please try to enable the authority plugin for dc.contributor.author. In your
dspace.cfg, uncomment these lines (remove the #):

plugin.named.org.dspace.content.authority.ChoiceAuthority = \
org.dspace.content.authority.LCNameAuthority = LCNameAuthority, \
choices.plugin.dc.contributor.author =  LCNameAuthority
choices.presentation.dc.contributor.author = lookup
authority.controlled.dc.contributor.author = true

Save your dspace.cfg and restart your tomcat server.

Regards,
euler



--
View this message in context: 
http://dspace.2283337.n4.nabble.com/ERROR-creating-index-discovery-tp4676311p4676317.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
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: creating index discovery‏

2015-01-22 Thread . .
Apologies, I had not put that running dspace index-discovery -f, I always get 
the following error:
ERROR org.dspace.discovery.SolrServiceImpl @ No choices plugin was configured 
for  field dc_contributor_author.java.lang.IllegalArgumentException: No 
choices plugin was configured for  field dc_contributor_author.   at 
org.dspace.content.authority.ChoiceAuthorityManager.getLabel(ChoiceAuthorityManager.java:243)
at 
org.dspace.content.authority.ChoiceAuthorityManager.getLabel(ChoiceAuthorityManager.java:231)
at 
org.dspace.browse.SolrBrowseCreateDAO.additionalIndex(SolrBrowseCreateDAO.java:219)
  at 
org.dspace.discovery.SolrServiceImpl.buildDocument(SolrServiceImpl.java:1393)   
 at 
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:215)  at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:387)   at 
org.dspace.discovery.IndexClient.main(IndexClient.java:127)  at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at 
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)  at 
java.lang.reflect.Method.invoke(Unknown Source)  at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225)   
 at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)


From: alsap...@hotmail.es
To: dspace-tech@lists.sourceforge.net
Date: Thu, 22 Jan 2015 12:09:48 +0100
Subject: [Dspace-tech] ERROR: creating index discovery‏




Thanks for the response.I am using the configuration file (dspace.cfg) of 
Versioned 4.2.I do not have active control authorities in this version.I copy 
of the file (dspace.cfg) for the control authorities, I have not touched 
anything in this configuration.#  Authority Control Settings  
##plugin.named.org.dspace.content.authority.ChoiceAuthority = \# 
org.dspace.content.authority.SampleAuthority = Sample, \# 
org.dspace.content.authority.LCNameAuthority = LCNameAuthority, \# 
org.dspace.content.authority.SHERPARoMEOPublisher = SRPublisher, \# 
org.dspace.content.authority.SHERPARoMEOJournalTitle = SRJournalTitle## The 
DCInputAuthority plugin is automatically configured with every## value-pairs 
element in input-forms.xml, namely:##   common_identifiers, common_types, 
common_iso_languages The DSpaceControlledVocabulary plugin is automatically 
configured## with every *.xml file in 
[dspace]/config/controlled-vocabularies,## and creates a plugin instance for 
each, using base filename as the name.## eg: nsi, srsc.## Each 
DSpaceControlledVocabulary plugin comes with three configuration options:# 
vocabulary.plugin._plugin_.hierarchy.store = true|false# default: true# 
vocabulary.plugin._plugin_.hierarchy.suggest = true|false  # default: true# 
vocabulary.plugin._plugin_.delimiter = string# default: 
:: An example using srsc can be found later in this 
section#plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \# 
org.dspace.content.authority.DCInputAuthority, \# 
org.dspace.content.authority.DSpaceControlledVocabulary## configure LC Names 
plugin#lcname.url = http://alcme.oclc.org/srw/search/lcnaf This sets the 
default lowest confidence level at which a metadata value is included## in an 
authority-controlled browse (and search) index.  It is a symbolic## keyword, 
one of the following values (listed in descending order):##   accepted##   
uncertain##   ambiguous##   notfound##   failed##   rejected##   novalue##   
unset## See manual or org.dspace.content.authority.Choices source for 
descriptions.authority.minconfidence = ambiguous## demo: use LC plugin for 
author#choices.plugin.dc.contributor.author =  
LCNameAuthority#choices.presentation.dc.contributor.author = 
lookup#authority.controlled.dc.contributor.author = true This sets the 
lowest confidence level at which a metadata value is included## in an 
authority-controlled browse (and search) index.  It is a symbolic## keyword 
from the same set as for the default 
authority.minconfidence#authority.minconfidence.dc.contributor.author = 
accepted## demo: subject code autocomplete, using srsc as authority## 
(DSpaceControlledVocabulary plugin must be enabled)## Warning: when enabling 
this feature any controlled vocabulary configuration in the input-forms.xml for 
the metadata field will be overridden.#choices.plugin.dc.subject = 
srsc#choices.presentation.dc.subject = 
select#vocabulary.plugin.srsc.hierarchy.store = 
true#vocabulary.plugin.srsc.hierarchy.suggest = 
true#vocabulary.plugin.srsc.delimiter = ::## Demo: publisher name lookup 
through SHERPA/RoMEO:#choices.plugin.dc.publisher = 
SRPublisher#choices.presentation.dc.publisher = suggest## demo: journal title 
lookup, with ISSN as authority#choices.plugin.dc.title.alternative = 
SRJournalTitle#choices.presentation.dc.title.alternative = 
suggest#authority.controlled.dc.title.alternative = true## demo: use choice 
authority (without authority

[Dspace-tech] ERROR: creating index discovery‏

2015-01-22 Thread . .
Thanks for the response.I am using the configuration file (dspace.cfg) of 
Versioned 4.2.I do not have active control authorities in this version.I copy 
of the file (dspace.cfg) for the control authorities, I have not touched 
anything in this configuration.#  Authority Control Settings  
##plugin.named.org.dspace.content.authority.ChoiceAuthority = \# 
org.dspace.content.authority.SampleAuthority = Sample, \# 
org.dspace.content.authority.LCNameAuthority = LCNameAuthority, \# 
org.dspace.content.authority.SHERPARoMEOPublisher = SRPublisher, \# 
org.dspace.content.authority.SHERPARoMEOJournalTitle = SRJournalTitle## The 
DCInputAuthority plugin is automatically configured with every## value-pairs 
element in input-forms.xml, namely:##   common_identifiers, common_types, 
common_iso_languages The DSpaceControlledVocabulary plugin is automatically 
configured## with every *.xml file in 
[dspace]/config/controlled-vocabularies,## and creates a plugin instance for 
each, using base filename as the name.## eg: nsi, srsc.## Each 
DSpaceControlledVocabulary plugin comes with three configuration options:# 
vocabulary.plugin._plugin_.hierarchy.store = true|false# default: true# 
vocabulary.plugin._plugin_.hierarchy.suggest = true|false  # default: true# 
vocabulary.plugin._plugin_.delimiter = string# default: 
:: An example using srsc can be found later in this 
section#plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \# 
org.dspace.content.authority.DCInputAuthority, \# 
org.dspace.content.authority.DSpaceControlledVocabulary## configure LC Names 
plugin#lcname.url = http://alcme.oclc.org/srw/search/lcnaf This sets the 
default lowest confidence level at which a metadata value is included## in an 
authority-controlled browse (and search) index.  It is a symbolic## keyword, 
one of the following values (listed in descending order):##   accepted##   
uncertain##   ambiguous##   notfound##   failed##   rejected##   novalue##   
unset## See manual or org.dspace.content.authority.Choices source for 
descriptions.authority.minconfidence = ambiguous## demo: use LC plugin for 
author#choices.plugin.dc.contributor.author =  
LCNameAuthority#choices.presentation.dc.contributor.author = 
lookup#authority.controlled.dc.contributor.author = true This sets the 
lowest confidence level at which a metadata value is included## in an 
authority-controlled browse (and search) index.  It is a symbolic## keyword 
from the same set as for the default 
authority.minconfidence#authority.minconfidence.dc.contributor.author = 
accepted## demo: subject code autocomplete, using srsc as authority## 
(DSpaceControlledVocabulary plugin must be enabled)## Warning: when enabling 
this feature any controlled vocabulary configuration in the input-forms.xml for 
the metadata field will be overridden.#choices.plugin.dc.subject = 
srsc#choices.presentation.dc.subject = 
select#vocabulary.plugin.srsc.hierarchy.store = 
true#vocabulary.plugin.srsc.hierarchy.suggest = 
true#vocabulary.plugin.srsc.delimiter = ::## Demo: publisher name lookup 
through SHERPA/RoMEO:#choices.plugin.dc.publisher = 
SRPublisher#choices.presentation.dc.publisher = suggest## demo: journal title 
lookup, with ISSN as authority#choices.plugin.dc.title.alternative = 
SRJournalTitle#choices.presentation.dc.title.alternative = 
suggest#authority.controlled.dc.title.alternative = true## demo: use choice 
authority (without authority-control) to restrict dc.type on EditItemMetadata 
page#choices.plugin.dc.type = common_types#choices.presentation.dc.type = 
select## demo: same idea for dc.language.iso#choices.plugin.dc.language.iso = 
common_iso_languages#choices.presentation.dc.language.iso = select# Change 
number of choices shown in the select in Choices lookup 
popup#xmlui.lookup.select.size = 12--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
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