Bram,
Unfortunately, we had no luck with the following. After adding the fields to
the schema.xml and deleting the index and reindexing, we found that they still
were appearing in the dropdown suggestions. I've included what we added below,
and the options around it as well, to show the general location we added it. I
had quick read through the schema.xml documentation on the apache site as well,
and so I can understand why it is supposed to work. My only guess would be that
if the order that things are added to the schema.xml is important, that it is
in the wrong place.
Thanks
Jennifer
<!--Date matching-->
<dynamicField name="*.year" type="sint" indexed="true" stored="true"
multiValued="true" omitNorms="true" />
<dynamicField name="*_dt" type="date" indexed="true" stored="true"
multiValued="true" omitNorms="true" />
<field name="dc.description.provenance" type="ignored" multiValued="true"/>
<field name="dc.rights" type="ignored" multiValued="true"/>
<field name="dc.description.provenancedonor" type="ignored"
multiValued="true"/>
<field name="dc.date.review" type="ignored" multiValued="true"/>
<field name="dc.identifier.email" type="ignored" multiValued="true"/>
<field name="dc.identifier.address" type="ignored" multiValued="true"/>
<field name="dc.identifier.phone" type="ignored" multiValued="true"/>
<field name="dc.ntl.rating" type="ignored" multiValued="true"/>
<field name="dc.ntl.withdrawn" type="ignored" multiValued="true"/>
<field name="dc.ntl.terms" type="ignored" multiValued="true"/>
<field name="dc.ntl.lift" type="ignored" multiValued="true"/>
<!--Used for matching on all other fields-->
<dynamicField name="*" type="text" multiValued="true"/>
Jennifer Whalan
Systems Support Officer | Innovation & Access
Northern Territory Library 'Celebrating 30 Years'
Department of Natural Resources, Environment, The Arts and Sport
Northern Territory Government
Phone: (08) 8922 0752
Fax: (08) 8922 0722
Email: [email protected]<mailto:[email protected]>
Web: www.ntl.nt.gov.au<http://www.ntl.nt.gov.au/>
The information contained in this message and any attachments may be
confidential information and may be subject to legal privilege, public interest
or legal profession privilege. If you are not the intended recipient, any use,
disclosure or copying of this message or any attachments is unauthorised. If
you have received this document in error, please advise the sender. No
representation or warranty is given that attached files are free from viruses
or other defects. The recipient assumes all responsibility for any loss or
damage resulting directly or indirectly from the use of any attached files.
________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Bram Luyten
Sent: Thursday, 21 April 2011 9:28 PM
To: Jennifer Whalan
Cc: Kevin Van de velde
Subject: Re: [Dspace-tech] Discovery and metadata.hide option in 1.7.1
Dear Jennifer,
recently, one of our developers responded to your question on the DSpace
mailing list. As @mire originally developed Mirage & Discovery for DSpace 1.7,
I would be very interested to learn if the given advice has helped you to
resolve your issue.
Furthermore, if you experience any other issue with Discovery and Mirage, we
can always take a look at it for resolving in one of the upcoming releases of
DSpace. Likewise, if you would have any challenging migration, upgrade or
customization tasks, I'd be happy to investigate whether our professional
services could apply in your context.
with kindest regards,
Bram Luyten
@mire
Technologielaan 9 - 3001 Heverlee - Belgium
2888 Loker Avenue East, Suite 305 - Carlsbad, CA 92010 - USA
atmire.com<http://atmire.com/> - Institutional Repository Solutions
On Thu, Apr 14, 2011 at 3:43 PM, Kevin Van de velde < > wrote:
Hi Jennifer,
The disallowing of indexing certain fields in discovery has not yet been
implemented. But if you want you can do this yourself by altering a single file.
The file that needs to be edited is the following:
{dspace.dir}/solr/search/conf/schema.xml. In the "fields" tag (it should start
somewhere around line 490 of the file) you just need to add the following line:
<field name="{field.not.to.index}" type="ignored" multiValued="true"/>
So for example if you do not want the title field to be indexed add:
<field name="dc.title" type="ignored" multiValued="true"/>
After this is done just restart the tomcat and re index discovery and the field
should be removed from the index.
I really hope this helps.
Ps: I do plan to create a patch to fix this issue (so that non indexable fields
can be configured) as soon as I find the time to create one.
Kind regards,
Kevin Van de Velde
@mire - www.atmire.com<http://www.atmire.com>
533 2nd Street - Encinitas, CA 92024 - USA
Technologielaan 9 - 3001 Heverlee - Belgium
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get Tog@ther
On 14 April 2011 08:45, Jennifer Whalan
<[email protected]<mailto:[email protected]>> wrote:
Not sure if this is perhaps a bug or not, but currently in our dspace.cfg, we
have about 8 metadata fields that we want to keep hidden from searches, item
views, oai, etc. However I've noticed that these fields are indexed by
Discovery, and so if doing a filter on Fulltext, the dropdown shows options
that are in these particular fields.
Is there a way to remove these fields from being indexed by Discovery?
Thanks
Jennifer.
Jennifer Whalan
Territory Stories Administrator
Innovation & Access, Northern Territory Library
Department of Natural Resources, Environment, The Arts and Sport
Northern Territory Government
Phone: (08) 8922 0752
Fax: (08) 8922 0722
Email: [email protected]<mailto:[email protected]>
Web: www.ntl.nt.gov.au<http://www.ntl.nt.gov.au/>
The information contained in this message and any attachments may be
confidential information and may be subject to legal privilege, public interest
or legal profession privilege. If you are not the intended recipient, any use,
disclosure or copying of this message or any attachments is unauthorised. If
you have received this document in error, please advise the sender. No
representation or warranty is given that attached files are free from viruses
or other defects. The recipient assumes all responsibility for any loss or
damage resulting directly or indirectly from the use of any attached files.
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
