Hi Claudia,
Thank you for your precious help, It was exactly what I needed.
Have a nice day,
Ludovic Reenaers
2010/3/25 Claudia Jürgen <[email protected]>
>
> Hello Ludovic,
>
> the configuration parameter will apply to any metadata field in DSpace.
> The form is:
>
> metadata.hide.SCHEMA.ELEMENT.QUALIFIER = true
> SCHEMA.ELEMENT.QUALIFIER can be any registered metadatafield.
>
> E.g. you got a schema administrative with a field acquisition and a
> qualifier price, to hide it you set
> metadata.hide.administrative.acquisition.price=true
>
>
> Hope that helps
>
> Claudia Jürgen
>
> Am 24.03.2010 19:11, schrieb Ludovic Reenaers:
>
> Hello Claudia,
>>
>> This seems to be the perfect solution. Thank you.
>> But if I understood well (since I'm not natively speaking english) the
>> commented lines, It is only applicable to Dublin Core schema. Am I right?
>>
>> Thank you for your help,
>>
>> Ludovic Reenaers
>>
>> 2010/3/24 Claudia Jürgen<[email protected]>
>>
>> Hello Ludovic,
>>>
>>> yes this is possible since 1.6.0.
>>>
>>> There is a configuration parameter to hide metadata from "public" view.
>>> Take a look at this section of the dspace.cfg:
>>>
>>> ##### 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
>>> # 3. OAI-PMH server, "oai_dc" format.
>>> # (NOTE: Other formats are _not_ affected.)
>>> # 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
>>>
>>>
>>> Hope that helps
>>>
>>> Claudia Jürgen
>>>
>>>
>>> Am 23.03.2010 20:33, schrieb Ludovic Reenaers:
>>>
>>> Hi everybody,
>>>>
>>>> Currently investigating the possibility to implement dspace for belgian
>>>> museums. The idea is to use dspace as a centralized and uniform solution
>>>> for
>>>> museum inventory management, getting benefits of OAI-PMH concept.
>>>>
>>>> The question is : considering an item described in a given custom
>>>> metadata
>>>> format, would it be possible to restrain anonymous user to see a given
>>>> item
>>>> property?
>>>> i.e : a painting has a inssurance value and a buy price... we want
>>>> Anonymous
>>>> users to be able to see all painting's properties but inssurance value
>>>> and
>>>> buy price.
>>>>
>>>> Can someone imagine a solution?
>>>>
>>>> thanks for your help,
>>>>
>>>> Ludovic Reenaers
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> DSpace-tech mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> DSpace-tech mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>>
>>>
>>>
>>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
