Re: [dspace-tech] Items list – no space between publisher names

[Franziska Ackermann]

Hi,

See 
https://wiki.duraspace.org/display/DSDOC6x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CustomizingMirage2

"Customizing Mirage2"

Hope this helps,
Franziska


Am 28.03.2017 um 15:08 schrieb admin:

Hello Franziska,

Thanks, indeed I followed this example and managed to add a collon to 
separate publisher names.


BTW, should I put the source aspect file to the following folder:
[dspace-source]/dspace/modules/xmlui-mirage2 ?
If yes, where exactly?

I am trying to figure out the proper workflow of what to modify and 
where, and documentation is sometimes still unclear to me :)




W dniu poniedziałek, 27 marca 2017 13:35:57 UTC+1 użytkownik Franziska 
Ackermann napisał:


Hi,

There are examples in item-list.xsl using "for-each", e.g.

https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/xsl/aspect/artifactbrowser/item-list.xsl#L285-L292

<https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/xsl/aspect/artifactbrowser/item-list.xsl#L285-L292>
In the example they use a semicolon to separate entries.

Hope his helps,
Franziska


Am 27.03.2017 um 13:55 schrieb admin:

Hello,


it a tiny thing, but I would like to correct it (and learn how to
do it).
Within a list of the newest items added to a collection, where
there is an information about a publisher, if there are more than
one publisher names, there is no space between them.

I suppose it is to be corrected somewhere in the item-list.xsl
(

I use DSpace 6.


Thanks,

Peter
-- 
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
<https://groups.google.com/group/dspace-tech>.
For more options, visit https://groups.google.com/d/optout
<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] Items list – no space between publisher names

[Franziska Ackermann]

Hi,

There are examples in item-list.xsl using "for-each", e.g. 
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/src/main/webapp/xsl/aspect/artifactbrowser/item-list.xsl#L285-L292

In the example they use a semicolon to separate entries.

Hope his helps,
Franziska


Am 27.03.2017 um 13:55 schrieb admin:

Hello,


it a tiny thing, but I would like to correct it (and learn how to do it).
Within a list of the newest items added to a collection, where there 
is an information about a publisher, if there are more than one 
publisher names, there is no space between them.


I suppose it is to be corrected somewhere in the item-list.xsl 
(


I use DSpace 6.


Thanks,

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

Re: [dspace-tech] Dspace 5 XMLUI - Add text and email to footer

[Franziska Ackermann]

Hi Tom,

You can do this in page-structure.xsl.

Best regards,
Franziska


Am 09.08.2016 um 01:54 schrieb Tom Avino:
I am new to XMLUI.  We have been using JSPUI for years.  I am trying 
to simply add one line of text and 2 names and email addresses.  Does 
anyone know how I can do this?

I know XMLUI is very different, but this should not be rocket science.

Tom
--
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] File visits during workflow / usage statistics

[Franziska Ackermann]

Dear list,

It seems that the "file visits" section in the XMLUI Usage Statistics 
takes visits into account that were done before(!) an ITEM was approved 
for entry into the archive. (DSpace 5.5, Mirage2).


This can lead to empty entries when files were substituted during the 
workflow. Example:



The empty entries stand for the names of the files that were opened 
during the workflow, and substituted by the user after his submission 
was rejected.


Do you agree that file visits should be counted from the point when the 
item is accepted into the archive? Otherwise this would mean a lot of 
empty entries when items are regularly rejected and its files 
substituted. These entries unfortunately don't have a meaning to users 
who visit the Usage Statistics Page.


Another matter is how to deal with files who are deleted at a later 
stage, after the approval of the item. At the moment DSpace displays an 
empty entry for deleted files too. In this second case it could make 
sense to keep track of the deleted file, because it used to be public. 
Some meaning could be added to help users understand the usage 
statistics better, e.g. [deprecated file].


I am looking forward to your views on this.

Best regards,
Franziska Ackermann

--
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: exclude display of values from certain metadata fields

[Franziska Ackermann]

Hi Monika,

There is a section in dspace.cfg which might help:

# Hide Item Metadata Fields  #
# Fields named here are hidden in the following places UNLESS the
# logged-in user is an Administrator:
#  1. XMLUI metadata XML view, and Item splash pages (long and short views).
#  2. JSPUI Item splash pages
# To designate a field as hidden, add a property here in the form:
#metadata.hide.SCHEMA.ELEMENT.QUALIFIER = true
#
# This default configuration hides the dc.description.provenance field,
# since that usually contains email addresses which ought to be kept
# private and is mainly of interest to administrators:
metadata.hide.dc.description.provenance = true

However, I am not sure whether it is sufficient for your purpose, 
because it only hides the metadata fields from the JSPUI Item Splash Pages.


Best regards,
Franziska Ackermann


Am 12.07.2016 um 15:44 schrieb Monika Mevenkamp:

I never got an answer to my question below.
I take this to mean: No there is no such feature that excludes values 
for a given list of metadata fields from the UI - unless logged in 
with the right privileges.


Does anybody have something similar implemented ?

Monika

—
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven



On Jul 8, 2016, at 4:12 PM, Monika Mevenkamp <mailto:mome...@gmail.com>> wrote:



Is it possible in JSPUI to define a no-show list  of metadata fields 
(used on items), such
that values for those fields will be shown only to users that are 
specially authorized.


I plan to build a custom feature that keeps track of status in 
metadata values; but I don’t
want regular users to be able to see those values. Along with this 
we’ll have employee
ids on items. While the ids are not a big secret we don’t want to 
advertise them broadly either,


Monika


—
Monika Mevenkamp
Digital Repository Infrastructure Developer
Princeton University
Phone: 609-258-4161
Skype: mo-meven





--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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.

Re: [dspace-tech] Re: [Dspace-tech] XMLUI Controlled vocabularies attribute closed not working

[Franziska Ackermann]

Hi,

We have the same experience. We are using DSpace 5.5, Mirage2. An 
alternative would be to offer a dropdown list instead via input-forms.xml.
However, this isn't very elegant for longer lists. Could you solve the 
problem?


Best regards,
Franziska Ackermann


Am 08.06.2016 um 14:06 schrieb Alan Orth:

Hi, Jacob. We have the SAME experience as you! We are using DSpace 5.1.

Does anyone know how to prevent the user from adding free-text
vocabulary terms when using controlled vocabularies?

Thank you,

On Thu, Sep 11, 2014 at 11:34 AM, Jacob Andersson
 wrote:

Hi,

The DSpace 4 documentation on "How to invoke a controlled vocabulary from 
input-forms.xml" states that

"The vocabulary element has an optional boolean attribute closed that can be used to force 
input only with the Javascript of controlled-vocabulary add-on. The default behaviour (i.e. without 
this attribute) is as set closed="false". This allow the user also to enter values as 
free text, not selecting them from the controlled vocabulary."

When I set closed="true" I see no effect in XMLUI (works fine in JSPUI though, 
stopping manual input).

Does anyone have any advice or similar experience?

Thanks,

---
Jacob Andersson
Librarian
Library & IT
Malmö University
205 06 Malmö
Sweden
+46-(0)40-66 58387
jacob.anders...@mah.se


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
DSpace-tech mailing list
dspace-t...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
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] Embargo and metadata dc.rights.accesRights in DSpace 5.5

[Franziska Ackermann]

Hi,

If the information is just needed for OpenAIRE, could you use the 
crosswalk to fetch it dynamically ?


I have seen this for various information on bitstreams in ore.xsl and 
mets.xsl, e.g. format, URL, size, checksum, ...
Could this be done for the access condition as well or is it stored 
differently ?


Best regards,
Franziska//Ackermann/
/


Am 09.06.2016 um 10:47 schrieb emilio lorenzo:


Hola Mariaangels

The best way is to program a curation task that reviews 
file-permisions, and suggest (or do) such change when that condition 
is detected.


Best luck

Emilio




El 09/06/2016 a las 10:27, Mariangels escribió:

Hola,

I'm working with DSPace 5.5 and xmlui Mirage theme.

In our repository we need always to fill the metadata:

/*dc.rights.accesRights*/

with this value:

/info:eu-repo/semantics/embargoedAccess/

when an item is embargoed.

When the embargoed is finished//I need to change this value and put:

/info:eu-repo/semantics/openAccess

/can DSpace 5.5 do this automatically when an embargo is finished?

Thanks in advance.










--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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.

Re: [dspace-tech] Additional button in sidebar

[Franziska Ackermann]

Hi,

Thanks for your code. I'd like the button to be displayed in the sidebar 
on every(!) page.
How would I change the code to achieve this (leaving out @n=... doesn't 
have the desired effect) ?


Best regards,
Franziska Ackermann



Am 08.06.2016 um 12:22 schrieb ORIOL OLIVÉ COMADIRA:

Sorry, I make a mistake!
I forgot the @:






-- Original Message --
From: "ORIOL OLIVÉ COMADIRA" <mailto:oriol.ol...@udg.edu>>
To: "Franziska Ackermann" <mailto:franziska.ackerm...@uni-ulm.de>>; "DSpace Technical Support" 
mailto:dspace-tech@googlegroups.com>>

Sent: 08/06/2016 12:01:14
Subject: Re: [dspace-tech] Additional button in sidebar

Hi Franziska,
you can do it by adding some code in navigation.xsl
for example something like this:

 

Best,
-- Original Message --
From: "Franziska Ackermann" <mailto:franziska.ackerm...@uni-ulm.de>>
To: "DSpace Technical Support" <mailto:dspace-tech@googlegroups.com>>

Sent: 08/06/2016 10:14:28
Subject: [dspace-tech] Additional button in sidebar

Hi,
To make it easier for users to start a new submission, I'd like to add
a
button in the sidebar before the "BROWSE" block (Mirage2).
Here a examples of what I mean:
https://mcstor.library.milligan.edu/
http://repositorioseea.es/
I'd be happy about hints on how to proceed.
Best regards,
Franziska Ackermann
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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] Additional button in sidebar

[Franziska Ackermann]

Hi,

To make it easier for users to start a new submission, I'd like to add a 
button in the sidebar before the "BROWSE" block (Mirage2).


Here a examples of what I mean:
https://mcstor.library.milligan.edu/
http://repositorioseea.es/

I'd be happy about hints on how to proceed.

Best regards,
Franziska Ackermann

--
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] BibTeX export

[Franziska Ackermann]

Hi,

JSPUI has a share bar which can be used to export bibliographic metadata 
in various formats.
Are there plans to offer this feature in DSpace 7.x as well when there 
will be a single user interface?


Best regards,
Franziska Ackermann


Am 25.05.2016 um 16:35 schrieb Oliver Goldschmidt:

Hello DSpacers,

I know, that there have been a couple of approaches to integrate a 
good BibTeX-export into DSpace. For instance, there are some tickets 
dealing with that issue: https://jira.duraspace.org/browse/DS-1224, 
https://jira.duraspace.org/browse/DS-1493 and 
https://jira.duraspace.org/browse/DS-2471. Obviously none of these 
approaches has got it into the DSpace distribution yet. Nevertheless I 
know some DSpace instances offering a BibTeX export for users, 
obviously using different ways to do that. I also know, that DSpace 
CRIS has something to export into BibTeX, but I am not very pleased 
about the quality of data and its obviously only working, when a user 
has logged in (which is not acceptable for our use case)... As DS-1493 
also has not been continued I'd like to ask again, if there is any way 
on DSpace 5.x or 6 to get DSpace records as BibTeX for anonymous users 
in a good (or at least configurable) data quality?


TIA,
Oliver
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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.

Re: [dspace-tech] Displays different information in the list of items (DSpace 5.5)

[Franziska Ackermann]

Hi Mariangels,

the search term (here: "predictor") was found in the fulltext of the 
item, so DSpace does not display the abstract but snippets of the full 
text where the search term was found.


You can fix this by commenting out

class="org.dspace.discovery.configuration.DiscoveryHitHighlightFieldConfiguration">







in discovery.xml.

Best regards,

Franziska Ackermann


Am 23.05.2016 um 11:49 schrieb Mariangels:


Hello,

I'm working with DSpace 5.5 and xmlui (Mirage theme)
I have a problem:

When I'm browsing through the communities, collections, etc. I can see 
this information about a record:


Title
Authors
Abstract
"Please you can see in the attached file1.jpg"

That's OK but when I search a record in Discovery I can see:

Title
Authors
and...surprisingly...
some content of the .pdf file  :-o
"Please you can see in the attached file2.jpg"

Can you help me? Why that happens?

--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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] Unwanted result when removing a special group

[Franziska Ackermann]

Hi,

We have a special group for people logging in via LDAP called "MYEDU". I 
removed this special group from the "COLLECTION_X_SUBMIT" group.
However, members of the special group can still submit to the collection 
(after logging out, cleaning the browser cache and logging in again).


As an administrator, I check a member's groups in the Admin UI (XMLUI, 
Mirage2) and don't see COLLECTION_X_SUBMIT in his list of groups.
When the member himself logs in and checks his groups, 
COLLECTION_X_SUBMIT is still in the list.


Any ideas why this is the case?

Best regards,
Franziska Ackermann

--
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] DSpace Licence - where is it?

[Franziska Ackermann]

Hi Gary,

Are you using XMLUI or JSPUI?

Best regards,
Franziska

Am 23.03.2016 um 01:57 schrieb Gary Browne:

Hi Claudia,

I still can't see a license file. I logged on as an administrator and 
had a look at the item page (no license visible there, as expected). 
Then I clicked "Edit..." but the list of bitstreams doesn't list any 
license (there is only the ORIGINAL bundle). Does this mean no license 
was submitted with this item or am I looking in the wrong place.


I have checked in the config directory and my changes to the default 
license are there.


Thanks again for your help.

Regards,G
Gary

On Wednesday, March 23, 2016 at 11:44:01 AM UTC+11, Gary Browne wrote:

Thanks very much Claudia,

That's exactly the information I needed.

Regards,
Gary

On Tuesday, March 22, 2016 at 7:16:09 PM UTC+11, Claudia Jürgen
wrote:

Hello Gary,

the item license is stored in the bundle LICENSE within the item.
It is usually not visibal to the end user, as the bitstream
for license
is marked as internal in the bitstream format registry.
So only admins can see it when the are in the edit item mode.
You can make the license accessible by setting the
configuration parameter:
webui.license.show=true
This will show a button to retrieve the license in the item
display.
As the license inherits the rights like any other bitstream,
it might
still be restricted.

The item got it's license either from the license defined in the
collection it is submitted to or from the default.license.

Hope this helps

Claudia



--
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] XMLUI Formatting Distribution License

[Franziska Ackermann]

Hi,

thanks for your advice. This works for Mirage2.

Best regards,
Franziska

Am 15.03.2016 um 16:21 schrieb Mark H. Wood:

On Tue, Mar 15, 2016 at 09:25:04AM +0100, Franziska Ackermann wrote:

We've recently noticed the same thing. Thanks for the links. It says
"Fix for Mirage only".
It would be nice to have this feature in Mirage2 as well.

There is no .../lib/css/style.css in the Mirage2 theme.
Can you give advise how to fix this when using Mirage2?

I have not worked with Mirage 2, but I would probably try putting
those declarations at the end of src/main/webapp/styles/_style.scss



--
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] XMLUI Formatting Distribution License

[Franziska Ackermann]

Hi,

We've recently noticed the same thing. Thanks for the links. It says 
"Fix for Mirage only".

It would be nice to have this feature in Mirage2 as well.

There is no .../lib/css/style.css in the Mirage2 theme.
Can you give advise how to fix this when using Mirage2?

Best regards,
Franziska


Am 14.03.2016 um 19:36 schrieb Mark H. Wood:

On Mon, Mar 14, 2016 at 05:34:02PM +, Cameron, Jacob wrote:

Is there a way to edit the default license and have html formatting
in the XMLUI version?  I have tried multiple things to try to get it
to work but I can't.  Right now my agreement looks like a giant wad of
text with no formatting.  We are running DSpace 1.8.2 and will be
upgrading in the near future to 5.

That will be fixed in the upcoming DSpace 6.0.  In the meantime, the
fix is fairly simple:

   https://github.com/DSpace/DSpace/pull/1001/files

Only a few HTML elements are supported:

   https://wiki.duraspace.org/display/DSDOC6x/Simple+HTML+Fragment+Markup



--
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] Private items

[Franziska Ackermann]

Hello,

Thank you very much for your help.

We would like to find a way to hide embargoed items (metadata + 
bitstream) completely, also from bots and APIs. However, neither the 
embargo nor the "private flag" nor a combination of both seems to be 
sufficient:


https://wiki.duraspace.org/display/DSDOC5x/DSpace+Item+State+Definitions:

Embargoed items
"If the metadata of the item should be visible only to a specific group 
of users, it is possible to define an embargo policy also for the ITEM 
itself.  A READ policy for a specific group will mean that only the 
users in that group will be able to access the item splash page. Note 
that currently only some UIs (JSPUI/XMLUI) and in a very specific 
configuration (discovery enabled as search provider, and the 
SOLRBrowseDAOs is used for the Browse system) are fully rights aware.  
This means that in different UIs or with different configurations 
(legacy lucene search or DBMS browse)  some metadata of a restricted 
item could be exposed to unauthorized users. When you need to work with 
UIs not fully rights aware, a workaround can be to use the "Private 
Item" flag to make the item undiscoverable so that metadata will be not 
exposed to unauthorized users."


We'd like to be sure that both bitstreams and metadata are completely 
hidden while the item is under embargo.


Do you have any suggestions how to achieve this?

Best regards,
Franziska


Am 09.03.2016 um 16:35 schrieb Claudia Jürgen:

Dear Franziska


Two questions about "private items":

1. Can items with a private flag be found by bots, so they will appear
in Google Scholar, for instance?

They are accessible by bots via the direct hit on the splash page e.g.
http://mydspaceinstance/handle/yourprefix/
If you provide sitemaps for Google everything will be indexed. But
Google Scholar uses more than just the sitemaps to aggregate the 
metadata.


If you do not use  the handle system but another persisten identifier
e.g. DOI than anything will be available via DataCite and thus
distributed and made visible.


2. Are private items discoverable via OAI-PMH or other APIs?

They are not searchable and not in any lists, but accessible as single
records.
E.g. in  OAI-PMH the should not appear in ListRecords/Idenfiers, but if
you know the identifier you cant retrieve them via GetRecord.

Hope this helps

Claudia Jürgen



We are using DSpace 5.4 with Mirage2.

Thank you and best regards,
Franziska






--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. 
Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht 
der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte 
den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung 
eines solchen Schriftstücks per Telefax erfolgen.


Important note: The information included in this e-mail is 
confidential. It is solely intended for the recipient. If you are not 
the intended recipient of this e-mail please contact the sender and 
delete this message. Thank you. Without prejudice of e-mail 
correspondence, our statements are only legally binding when they are 
made in the conventional written form (with personal signature) or 
when such documents are sent by fax.




--
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] Private items

[Franziska Ackermann]

Thank you for your quick response,

The page

https://wiki.duraspace.org/display/DSDOC5x/DSpace+Item+State+Definitions

dates back to November 2013. Is it still up-to-date?

Have the developers been working on the discoverability of "private 
items" since then? A short info would be much appreciated.


Best regards,
Franziska



Am 09.03.2016 um 16:03 schrieb Kleiner Eike (klie):

Dear Franziska

I asked myself the exactly the same question today and found this great piece 
of documentation which should answer your questions:

https://wiki.duraspace.org/display/DSDOC5x/DSpace+Item+State+Definitions

Best Regards
Eike
--
ZHAW Zürcher Hochschule für Angewandte Wissenschaften
Hochschulbibliothek

Eike Kleiner
Turbinenstrasse 2
Postfach
CH-8401 Winterthur

Tel: +41 58 934 4959 / Fax: +41 58 935 4959
eike.klei...@zhaw.ch / www.zhaw.ch/library


-Ursprüngliche Nachricht-
Von: dspace-tech@googlegroups.com [mailto:dspace-tech@googlegroups.com] Im 
Auftrag von Franziska Ackermann
Gesendet: Mittwoch, 9. März 2016 16:00
An: DSpace Technical Support
Betreff: [dspace-tech] Private items

Dear list,

Two questions about "private items":

1. Can items with a private flag be found by bots, so they will appear in 
Google Scholar, for instance?
2. Are private items discoverable via OAI-PMH or other APIs?

We are using DSpace 5.4 with Mirage2.

Thank you and best regards,
Franziska




--
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] Private items

[Franziska Ackermann]

Dear list,

Two questions about "private items":

1. Can items with a private flag be found by bots, so they will appear 
in Google Scholar, for instance?

2. Are private items discoverable via OAI-PMH or other APIs?

We are using DSpace 5.4 with Mirage2.

Thank you and best regards,
Franziska




--
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] Adding new metadata for single collection on DSpace

[Franziska Ackermann]

Hello,

This is possible. You can create collection-specific input-forms.

https://wiki.duraspace.org/display/DSDOC5x/Submission+User+Interface#SubmissionUserInterface-CustomMetadata-entryPagesforSubmission

Best regards,
Franziska Ackermann


Am 01.03.2016 um 14:43 schrieb Lewatle Johannes Phaladi:

Dear All,

I would like to add new metadata fields and those fields should not 
appear on global collections but only become available for individual 
collection. Please advise if this is possible or not.


Regards,
Lewatle
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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.

Re: [dspace-tech] Harvesting EPrints repository from DSpace

[Franziska Ackermann]

Hi,

What worked for me was the solution described under the link you sent below.
After the file "OAI_Bibliography.pm" had been removed from the E-Prints 
Repository, DSpace could harvest the records via oai_dc.


Best regards,
Franziska


Am 25.02.2016 um 17:12 schrieb amgcia...@gmail.com:

Hi all,

We are running a DSpace repository and would like to harvest metadata 
from an EPrints repository.


We have successfully configured a collection that harvests its content 
from an external source, in this case an EPrints repository OAI feed 
(selecting an specific OAI set). DSpace connects successfully to the 
EPrints OAI server, however it’s only retrieving empty metadata 
records. We are experiencing the same issue as described here 
.


We have looked at the DSpace code and located the issue: DSpace’s 
harvester module requests first a list of supported metadata formats 
to find the metadata prefix that the target repository uses for the 
selected metadata schema (http://www.openarchives.org/OAI/2.0/oai_dc). 
Internally this is done by iterating through the results of the 
ListMetadataFormats query and returns the metadataPrefix for the first 
metadataFormat that matches the selected metadata schema.


What happens in this case is that EPrints has more than one entry for 
the supported metadata formats using OAI_DC (oai_bibl and oai_dc 
prefixes):


…

  oai_bibl
http://www.openarchives.org/OAI/2.0/oai_dc.xsd
http://www.openarchives.org/OAI/2.0/oai_dc/


  oai_dc
http://www.openarchives.org/OAI/2.0/oai_dc.xsd
http://www.openarchives.org/OAI/2.0/oai_dc/

…

DSpace’s harvester is then selecting the first metadataPrefix, i.e. 
oai_bibl, for which EPrints is returning records with no metadata.


Just wondering if anyone has experienced the same issue, and if so, 
how did they solve it. Any help/suggestions are very much appreciated. 
Ideally we would like to avoid customising DSpace just to fix this, so 
I’m wondering whether there’s an easy way to fix this through EPrints 
configuration: e.g. disabling oai_bibl or something similar.


Many thanks and kind regards,
Agustina
--
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.

Re: [dspace-tech] Harvester stops

[Franziska Ackermann]

Dear list,

The problem I described earlier on the list unfortunately hasn't been 
resolved.
When I initiate a harvest process from the command line (DSpace 5.3), 
the harvester still stops after some time and throws an error.

/"java.lang.OutOfMemoryError: Java heap space"/
or
/"java.lang.OutOfMemoryError: GC overhead limit exceeded" .//
/
Are there institutions who encountered the same problem and found a way 
to fix it?


The settings in oai.cfg are:

### Harvester settings

# Crosswalk settings; the {name} value must correspond to a declared 
ingestion crosswalk

# harvester.oai.metadataformats.{name} = {namespace},{optional display name}
# The display name is only used in the xmlui; for the jspui there are 
entries in the
# Messages.properties in the form 
jsp.tools.edit-collection.form.label21.select.{name}
harvester.oai.metadataformats.dc = 
http://www.openarchives.org/OAI/2.0/oai_dc/, Simple Dublin Core
harvester.oai.metadataformats.qdc = http://purl.org/dc/terms/, Qualified 
Dublin Core
harvester.oai.metadataformats.dim = 
http://www.dspace.org/xmlns/dspace/dim, DSpace Intermediate Metadata


# This field works in much the same way as 
harvester.oai.metadataformats.PluginName

# The {name} must correspond to a declared ingestion crosswalk, while the
# {namespace} must be supported by the target OAI-PMH provider when 
harvesting content.

# harvester.oai.oreSerializationFormat.{name} = {namespace}

# Determines whether the harvester scheduling process should be started
# automatically when the DSpace webapp is deployed.
# default: false
harvester.autoStart=false

# Amount of time subtracted from the "from" argument of the OAI-PMH 
request to account
# for the time taken to negotiate a connection. Measured in seconds. 
Default value is 120.

#harvester.timePadding = 120

# How frequently the harvest scheduler checks the remote provider for 
updates,

# measured in minutes. The default value is 12 hours (or 720 minutes)
#harvester.harvestFrequency = 720
harvester.harvestFrequency = 1440

# The heartbeat is the frequency at which the harvest scheduler queries 
the local
# database to determine if any collections are due for a harvest cycle 
(based on
# the harvestFrequency) value. The scheduler is optimized to sleep after 
the check until the

# next collection is actually ready to be harvested. The minHeartbeat and
# maxHeartbeat are the lower and upper bounds on this timeframe. 
Measured in seconds.

# Default minHeartbeat is 30.  Default maxHeartbeat is 3600.
#harvester.minHeartbeat = 30
#harvester.maxHeartbeat = 3600

# How many harvest process threads the scheduler can spool up at once. 
Default value is 3.

#harvester.maxThreads = 3
harvester.maxThreads = 1

# How much time passes before a harvest thread is terminated. The 
termination process
# waits for the current item to complete ingest and saves progress made 
up to that point.

# Measured in hours. Default value is 24.
#harvester.threadTimeout = 24
harvester.threadTimeout = 4

# When harvesting an item that contains an unknown schema or field 
within a schema what
# should the harvester do? Either add a new registry item for the field 
or schema, ignore
# the specific field or schema (importing everything else about the 
item), or fail with

# an error. The default value if undefined is: fail.
# Possible values: 'fail', 'add', or 'ignore'
harvester.unknownField  = add
harvester.unknownSchema = fail

# The webapp responsible for minting the URIs for ORE Resource Maps.
# If using oai, the dspace.oai.uri config value must be set.
# The URIs generated for ORE ReMs follow the following convention for 
both cases.

# format: [baseURI]/metadata/handle/[theHandle]/ore.xml
# Default value is oai
#ore.authoritative.source = oai

# A harvest process will attempt to scan the metadata of the incoming items
# (dc.identifier.uri field, to be exact) to see if it looks like a handle.
# If so, it matches the pattern against the values of this parameter.
# If there is a match the new item is assigned the handle from the 
metadata value

# instead of minting a new one. Default value: hdl.handle.net
#harvester.acceptedHandleServer = hdl.handle.net, handle.myu.edu

# Pattern to reject as an invalid handle prefix (known test string, for 
example)
# when attempting to find the handle of harvested items. If there is a 
match with
# this config parameter, a new handle will be minted instead. Default 
value: 123456789.

#harvester.rejectedHandlePrefix = 123456789, myTestHandle

Allocated memory:
/JAVA_OPTS="-Xmx2048M -Xms2048M -XX:MaxPermSize=512m/

Help would be much appreciated.

Best regards,
Franziska Ackermann



Am 20.01.2016 um 15:19 schrieb Franziska Ackermann:

Dear list,

When I initiate a harvest process from the command line (DSpace 5.3), 
the harvester stops after some time and throws an error.

/"java.lang.OutOfMemoryError: Java heap space"/
or
/"java.lang.OutOfMemor

[dspace-tech] Harvester stops

[Franziska Ackermann]

Dear list,

When I initiate a harvest process from the command line (DSpace 5.3), 
the harvester stops after some time and throws an error.

/"java.lang.OutOfMemoryError: Java heap space"/
or
/"java.lang.OutOfMemoryError: GC overhead limit exceeded" .//
/
When I reboot and start the harvest process from the command line again, 
the harvester works but after some time it stops again and throws one of 
the above errors.


Did others have the same problem? How did you fix it?
We've checked the allocated heap memory, which should be fine.
/JAVA_OPTS="-Xmx2048M -Xms2048M  -XX:MaxPermSize=512m/

Is the problem related to https://jira.duraspace.org/browse/DS-1802 ?

Best regards,
Franziska Ackermann

--
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] [xmlui2] show logo in community-list

[Franziska Ackermann]

Hi,

In which path did you make these modifications?

Best regards,
Franziska Ackermann

Am 17.12.2015 um 16:30 schrieb Michael Wagner:

Dear all,

I'm using DSpace 5.3 with xmlui2 and want to show the community logos 
not only in the community view but also in the list of communities 
(e.g. the front page).


I already tried to modify

xsl/preprocess/communitylist.xsl
xsl/aspect/artifactbrowser/community-list.xsl

by adding select="./mets:fileSec/mets:fileGrp[@USE='LOGO']"/> but this doesn't 
work for me :(


Any hints how to do this?

Thanks and best regards,
Michael
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto: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] Harvester - Out of memory error

[Franziska Ackermann]

Dear list,

Has there been a fix for https://jira.duraspace.org/browse/DS-1802 ?

It's about a memory error that occurs when starting the oai-pmh harvester.
In my case, I didn't start the error from the xml user interface (as 
described in DS-1802), but from the command line. The error happens all 
the same:


**
Initializing the harvester... success.
Harvest started...
Exception: Java heap space
java.lang.OutOfMemoryError: Java heap space
at 
org.dspace.storage.rdbms.DatabaseManager.process(DatabaseManager.java:1008)
at 
org.dspace.storage.rdbms.TableRowIterator.next(TableRowIterator.java:151)

at org.dspace.content.MetadataField.findAll(MetadataField.java:312)
at 
org.dspace.content.DSpaceObject.getMetadataField(DSpaceObject.java:1199)

.
**

Best regards,
Franziska Ackermann

--
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] Mapping during ingestion (OAI-PMH)

[Franziska Ackermann]

Thank you for your quick reply. I am on the harvester side.
I was wondering if there is a file such as oai_dc.xsl for the ingest, 
but unfortunately it appears there isn't.


Best regards,
Franziska Ackermann


Am 03.12.2015 um 15:05 schrieb helix84:
Yes, it's possible on the OAI provider side. I don't think it's easily 
possible on the harvester side.


It could be as easy as changing oai_dc.xsl, which is described here:
https://wiki.duraspace.org/display/DSDOC5x/OAI+2.0+Server#OAI2.0Server-Add/RemoveMetadataFormats

Use  or  here:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L76

(not tested)

 habilitationThesis
 
 
 
 
 


However, I'd recommend you make a copy of oai_dc.xsl under a different 
name and make the modified oai_dc available via a different context 
(e.g. http://example.com/oai/myrequest). That should make future 
upgrades easier.


Please remember that after any change to .xsl files, you have to run
[dspace]/bin/dspace oai clean-cache


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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Mapping during ingestion (OAI-PMH)

[Franziska Ackermann]

Dear list,

I am harvesting a repository via OAI-PMH, using oai_dc. I'd like to 
change some metadata values during the process, e.g.:
dc:type with value "habilitation_thesis" on the data provider's side => 
dc:type with value "habilitationThesis" in our repository.


How would you do this?

Best regards,
Franziska Ackermann

--
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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] My Export in Dspace 5.4

[Franziska Ackermann]

Hi, go to a community / collection / item and click on "Export 
community" / "Export collection" / "Export item" in the sidebar.


There's a documentation on DSpace which might help you with your 
questions as well:

https://wiki.duraspace.org/display/DSDOC5x/DSpace+5.x+Documentation

Best regards,
Franziska Ackermann

Am 27.11.2015 um 17:29 schrieb Faiyaz Ahmed:

Hi,

Appreciated for your reply !!

Yes exactly, My Exports in the sidebar.

How I can do an export? Can you please send me the guide link or any 
command have?


Regards,

Faiyaz Ahmed

On Friday, November 27, 2015 at 9:16:39 PM UTC+5, Franziska Ackermann 
wrote:


Hi,

Do you mean "My Exports" in the sidebar? I believe the button
doesn't appear unless you have already done an export.

Best regards,
Franziska Ackermann


Am 27.11.2015 um 15:10 schrieb Faiyaz Ahmed:

Hello Everyone,

I really appreciate to everyone that, helping me on time.

I have a problem that how I can use this option "MyExport" as
like in demo below URL:

http://demo.dspace.org/xmlui/admin/export
<http://demo.dspace.org/xmlui/admin/export>

The Feature name is my export. I can not see at my localhost
after installing Dspace 5.4 version.

Does any one know that how I can enable this "MyExport" option.


Regards,
Faiyaz Ahmed


-- 
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 http://groups.google.com/group/dspace-tech
<http://groups.google.com/group/dspace-tech>.
For more options, visit https://groups.google.com/d/optout
<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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] My Export in Dspace 5.4

[Franziska Ackermann]

Hi,

Do you mean "My Exports" in the sidebar? I believe the button doesn't 
appear unless you have already done an export.


Best regards,
Franziska Ackermann


Am 27.11.2015 um 15:10 schrieb Faiyaz Ahmed:

Hello Everyone,

I really appreciate to everyone that, helping me on time.

I have a problem that how I can use this option "MyExport" as like in 
demo below URL:


http://demo.dspace.org/xmlui/admin/export

The Feature name is my export. I can not see at my localhost after 
installing Dspace 5.4 version.


Does any one know that how I can enable this "MyExport" option.


Regards,
Faiyaz Ahmed


--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Verified on demo machine - Bug "take task" during workflow process

[Franziska Ackermann]

Thank you, helix, for creating the bug report.

I found another bug related to the submission form: 
https://jira.duraspace.org/browse/DS-2922


If someone could point us to the file which needs editing, we'd be happy 
to look into it.


Best regards,
Franziska Ackermann

Am 25.11.2015 um 18:24 schrieb helix84:

I created a bug report on your behalf (bugs reported on the mailing
lists are usually forgotten):

https://jira.duraspace.org/browse/DS-2920


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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Verified on demo machine - Bug "take task" during workflow process

[Franziska Ackermann]

Hi,

I could verify the error I described earlier on the demo machine (XMLUI, 
5.4).
As described below, the error only happens when a user with 
Workflow-Step rights and without administrator rights tries to take an 
item from the pool by clicking the "take task" button.





Best regards,
Franziska Ackermann



Am 23.11.2015 um 14:50 schrieb Franziska Ackermann:

Dear list,

I believe I found a bug related to the "take task" button during the 
workflow process.


As an _administrator_, I click on "take task" and the item is assigned 
to me to be reviewed.
As a _non-administrato__r__with workflow step rights_ (let's say 
"Reviewer1"), I click on "take task" and get this error:


You are not allowed to perform this task.

Java stacktrace: org.dspace.authorize.AuthorizeException: You are not 
allowed to perform this task. at 
org.dspace.app.xmlui.aspect.workflow.FlowUtils.authorizeWorkflowItem(FlowUtils.java:164) 
at sun.reflect.GeneratedMethodAccessor228.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:606) at 
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155) at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243) at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237) at 
org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) 
at 
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) 
at 
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) 
at org.mozilla.javascript.Context.call(Context.java:538) at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)



However, the item is assigned to "Reviewer1" in the database. This 
becomes evident when you reload the submission page. The item will 
then appear under "Tasks you own".


Do you have any suggestions on how to fix this?

Best regards,
Franziska Ackermann

--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Bug "take task" during workflow process

[Franziska Ackermann]

Dear list,

I believe I found a bug related to the "take task" button during the 
workflow process.


As an _administrator_, I click on "take task" and the item is assigned 
to me to be reviewed.
As a _non-administrato__r__with workflow step rights_ (let's say 
"Reviewer1"), I click on "take task" and get this error:


You are not allowed to perform this task.

Java stacktrace: org.dspace.authorize.AuthorizeException: You are not 
allowed to perform this task. at 
org.dspace.app.xmlui.aspect.workflow.FlowUtils.authorizeWorkflowItem(FlowUtils.java:164) 
at sun.reflect.GeneratedMethodAccessor228.invoke(Unknown Source) at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:606) at 
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155) at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243) 
at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237) 
at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) 
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) 
at 
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) 
at 
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) 
at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) 
at org.mozilla.javascript.Context.call(Context.java:538) at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)



However, the item is assigned to "Reviewer1" in the database. This 
becomes evident when you reload the submission page. The item will then 
appear under "Tasks you own".


Do you have any suggestions on how to fix this?

Best regards,
Franziska Ackermann

--
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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] URL Mapping in XML UI

[Franziska Ackermann]

Hi,

as for "4 - When I logged in, then it will redirect 
to http://localhost:8080/xmlui/community-list.";


https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L1948-L1953

Best regards,
Franziska Ackermann

Am 19.11.2015 um 14:42 schrieb Faiyaz Ahmed:

Hello All,

Hope all you doing well. I have an requirement to change some in URL 
mapping. Below I have defined steps.


1- The Default URL is : http://localhost:8080/xmlui/
2- I want to change it to :http://localhost:8080/xmlui/password-login .
3- Any time I open the http://localhost:8080/xmlui/ it should redirect 
to http://localhost:8080/xmlui/password-login.
4 - When I logged in, then it will redirect 
to http://localhost:8080/xmlui/community-list.
5 - When I logged out, then it will back to 
http://localhost:8080/xmlui/password-login.


Does any one know how I can fulfill my above requirement in Dspace 5.3 
version with Mirage2 theme.


Regards,
Faiyaz Ahmed
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Collection template & OAI-PMH

[Franziska Ackermann]

Thank you, helix. It worked.

Am 19.11.2015 um 12:37 schrieb helix84:

I understand now, I didn't realize you're talking about harvesting
into DSpace, but of course only that makes sense.

I haven't tested it, but I believe it could work if you change "false"
to "true" here:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/harvest/OAIHarvester.java#L504


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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Collection template & OAI-PMH

[Franziska Ackermann]

Hi helix,

Here's what I found:
https://github.com/DSpace/DSpace/blob/master/dspace/config/dspace.cfg#L612-L613

Best regards,
Franziska Ackermann

Am 19.11.2015 um 12:22 schrieb helix84:

On Thu, Nov 19, 2015 at 12:08 PM, Franziska Ackermann wrote:

At the moment the collection template (fixed metadata field entries for
every item of a collection) is not applied to items which are harvested into
the collection via OAI-PMH.

As far as I know, the template is only applied during item submission.
Even if you change the template later, the changes are not applied to
existing items.


I have found such a switch for METS, but not for OAI-PMH.

Could you please describe what you found?


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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Collection template & OAI-PMH

[Franziska Ackermann]

Dear list,

At the moment the collection template (fixed metadata field entries for 
every item of a collection) is not applied to items which are harvested 
into the collection via OAI-PMH.
Is there a "switch" which allows me to decide whether the collection 
template is applied to harvested items or not?

I have found such a switch for METS, but not for OAI-PMH.

Best regards,
Franziska Ackermann

--
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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] FW: help link

[Franziska Ackermann]

Hello,

You could use page-structure.xml of your theme (Mirage, Mirage2, ...?) 
and insert the link to the website in the footer.


Best regards,
Franziska Ackermann

Am 06.11.2015 um 08:58 schrieb Saidy Binta:


*From:*dspace-tech@googlegroups.com 
[mailto:dspace-tech@googlegroups.com] *On Behalf Of *Saidy Binta

*Sent:* 05 November 2015 15:23
*To:* dspace-tech@googlegroups.com
*Subject:* [dspace-tech] help link

Dear All,

We are using dspace 5.1 xmlui and we want to implement a help link to a
html document on our repository. I have already created the help document
but I cannot link it to dspace.  If anyone have implement help links 
kindly help direct us to the right path.  Thanks


Regards
Binta




DISCLAIMER: This message is private and confidential. If you have 
received this message in error please notify us and remove it from 
your system. Any views and opinions expressed in this message are 
those of the individual sender and do not necessarily represent the 
views and opinions of Medical Research Council Unit, The Gambia


___
This communication is confidential and may contain privileged 
information intended solely for the named recipient(s). It may not be 
used or disclosed except for the purpose for which it has been sent. 
If you are not the intended recipient, you must not copy, distribute, 
take any action or reliance on it. If you have received this 
communication in error, do not open any attachments but please notify 
the Help Desk by e-mailing h...@mrc.gm <mailto:h...@mrc.gm> quoting 
the sender details, and then delete this message along with any 
attached files. E-mail messages are not secure and attachments could 
contain software viruses which may damage your computer system. Whilst 
every reasonable precaution has been taken to minimise this risk, The 
MRC Unit The Gambia cannot accept any liability for any damage 
sustained as a result of these factors. You are advised to carry out 
your own virus checks before opening any attachments. Unless expressly 
stated, opinions in this message are those of the e-mail author and 
not of the Medical Research Council Unit The Gambia.



--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] "Fields to Index for Search" in dspace.cfg vs. search filters in discovery.xml

[Franziska Ackermann]

Thank you, Tim.
Since the Discovery Module is now used by default, would it make sense 
to add some information in dspace.cfg?


For instance:

# Fields to Index for Search when you are using the traditional 
Lucene-based search engine #

## Not relevant if you are using the Discovery Module ##

# DC metadata elements.qualifiers to be indexed for search
# format: - search.index.[number] = [search field]:element.qualifier
#   - * used as wildcard
#- inputform -> In case we have different input-forms for different 
repository supported locales (e.g input-forms_el.xml, input-forms_pt.xml 
etc). In this case, the
#stored and the displayed value from all input-forms are 
indexed. If the stored value is not found in input-forms, it is indexed 
anyway.

#e.g.:search.index.12 = language:dc.language:inputform
#
###  changing these will change your search results, ###
###  but will NOT automatically change your search displays  ###


Best regards,
Franziska

Am 03.11.2015 um 21:43 schrieb Tim Donohue:

Hi Franziska,

Sorry for the late response.  However, I can verify that those 
"search.index.*" fields in the dspace.cfg are NOT used by the 
Discovery Module.


The "search.index.*" fields are only used if you are still utilizing 
the traditional Lucene-based search engine (which is no longer used by 
default, and has been deprecated in favor of Discovery).


- Tim

On 10/23/2015 4:04 AM, Franziska Ackermann wrote:

Dear list,

Is the section below from dspace.cfg relevant for the latest DSpace 
versions that use the Discovery Module?
Since the fields for advanced search can be configured in 
discovery.xml I am wondering whether the section below has become 
redundant.**


Best regards,
Franziska Ackermann


# Fields to Index for Search #

# DC metadata elements.qualifiers to be indexed for search
# format: - search.index.[number] = [search field]:element.qualifier
#   - * used as wildcard
#- inputform -> In case we have different input-forms for 
different repository supported locales (e.g input-forms_el.xml, 
input-forms_pt.xml etc). In this case, the
#stored and the displayed value from all input-forms are 
indexed. If the stored value is not found in input-forms, it is 
indexed anyway.

#e.g.:search.index.12 = language:dc.language:inputform
#
###  changing these will change your search results, ###
###  but will NOT automatically change your search displays  ###

search.index.1 = author:dc.contributor.*
search.index.2 = author:dc.creator.*
search.index.3 = title:dc.title.*
search.index.4 = keyword:dc.subject.*
search.index.5 = abstract:dc.description.abstract
search.index.6 = author:dc.description.statementofresponsibility
search.index.7 = series:dc.relation.ispartofseries
search.index.8 = abstract:dc.description.tableofcontents
search.index.9 = mime:dc.format.mimetype
search.index.10 = sponsor:dc.description.sponsorship
search.index.11 = identifier:dc.identifier.*
search.index.12 = language:dc.language.iso
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: How to enable new metadata format not related with DC

[Franziska Ackermann]

Hi,

It looks like you simply changed the name of your form. I don't know 
what advice you got, but if you haven't done so already, I would check 
if you included the "required" tag for every field in input-form.xml.


Example:


dc

contributor

author

true

Authors

name

Enter the names of the authors of this item.
*=>*
    
  


Best regards,
Franziska Ackermann


Am 01.11.2015 um 04:39 schrieb Wagner Pinheiro:
Hi. After sending my question, I' ve got one answer from someone on 
the list. Thank very much. I followed the instruction but now i get 
this message:



  Error creating submission forms: org.xml.sax.SAXException: Required
  field dc-element missing on page 1 of form engenharia


engenharia is my form name

On Friday, October 30, 2015 at 9:25:55 PM UTC-2, Wagner Pinheiro wrote:

Hello,

I've created a new metadata format for a specific information. But
, when I try to implement it, I receive this message:


  Error creating submission forms: org.xml.sax.SAXException:
  Required field dc-element missing on page 1 of form two


  two form is the name I gave for my form. Is it possible to have
  a totally new format without Dublin Core?


Wagner Pinheiro

Librarian
Universidade de São Paulo



--
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 
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To post to this group, send email to dspace-tech@googlegroups.com 
<mailto:dspace-tech@googlegroups.com>.

Visit this group at http://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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] "Fields to Index for Search" in dspace.cfg vs. search filters in discovery.xml

[Franziska Ackermann]

Dear list,

Is the section below from dspace.cfg relevant for the latest DSpace 
versions that use the Discovery Module?
Since the fields for advanced search can be configured in discovery.xml 
I am wondering whether the section below has become redundant.**


Best regards,
Franziska Ackermann


# Fields to Index for Search #

# DC metadata elements.qualifiers to be indexed for search
# format: - search.index.[number] = [search field]:element.qualifier
#   - * used as wildcard
#- inputform -> In case we have different input-forms for different 
repository supported locales (e.g input-forms_el.xml, input-forms_pt.xml 
etc). In this case, the
#stored and the displayed value from all input-forms are 
indexed. If the stored value is not found in input-forms, it is indexed 
anyway.

#e.g.:search.index.12 = language:dc.language:inputform
#
###  changing these will change your search results, ###
###  but will NOT automatically change your search displays  ###

search.index.1 = author:dc.contributor.*
search.index.2 = author:dc.creator.*
search.index.3 = title:dc.title.*
search.index.4 = keyword:dc.subject.*
search.index.5 = abstract:dc.description.abstract
search.index.6 = author:dc.description.statementofresponsibility
search.index.7 = series:dc.relation.ispartofseries
search.index.8 = abstract:dc.description.tableofcontents
search.index.9 = mime:dc.format.mimetype
search.index.10 = sponsor:dc.description.sponsorship
search.index.11 = identifier:dc.identifier.*
search.index.12 = language:dc.language.iso

--
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 http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.