Hi Judit, this has practically nothing to do with Embargo. You set embargo on an item level (or newly, I think, also on an object level - item, bundle, bitstream). It doesn't work on individual metadata fields which belong to an item.
But DSpace does have a feature that allows you to hide individual metadata fields from public view. It hides the field from all items, not just selected ones, so you'll have to put the interviewees in an individual field (e.g. local.contributors.interviewee, assuming you have a schema named "local"). So assuming your field is local.contributors.interviewee, in dspace.cfg set: metadata.hide.local.contributors.interviewee = true and restart DSpace. IIRC, this hides it from JSPUI and XMLUI, but not from OAI (another procedure is needed here) or LNI, so let me know if you use those. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
