[
https://jira.duraspace.org/browse/DS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20287#action_20287
]
Mark Diggory commented on DS-800:
---------------------------------
tdonohue: Next up: DS-800
[1:14pm] kompewter: [ https://jira.duraspace.org/browse/DS-800 ] - [#DS-800]
Manage visibilty of metadata fields as field attribute rather than in
dspace.cfg - DuraSpace JIRA
[1:15pm] tdonohue: hmm.. this one (Ds-800) is marked as "Addressed By" DS-655,
which robint is handling. But, it looks like robint didn't make it today
[1:15pm] kompewter: [ https://jira.duraspace.org/browse/DS-655 ] - [#DS-655]
MetadataExposure hides fields except for System Admins - this should extend to
Community and Collection Admins - DuraSpace JIRA
[1:15pm] mdiggory: visibility needs to be managed in the Model
[1:16pm] mdiggory: not in configuration files... and to expand on this we need
something like Metadata Bundles which would have ResourcePolicies attached
[1:16pm] tdonohue: mdiggory -- yea, it looks like that is robint's
recommendation down in the comments
[1:16pm] mdiggory: So that we can have system, descriptive, administrative,
bitstream metadata sections in a DSpace Item
[1:17pm] mdiggory: and align completely with METS metadata sections and
possibly align with Fedora Datastreams that are metadata centric
[1:17pm] sandsfish: perhaps this is an architecture question that needs some
further hashing out/design.
[1:17pm] sandsfish: i can see the work taking on a few different shapes/sizes.
[1:18pm] tdonohue: Maybe we should follow up with robint on this one?..I'd like
to here how this overlaps with other linked issues, etc
[1:18pm] mdiggory: tdonohue: yes I'm expanding on Robins suggestion....
> Manage visibilty of metadata fields as field attribute rather than in
> dspace.cfg
> --------------------------------------------------------------------------------
>
> Key: DS-800
> URL: https://jira.duraspace.org/browse/DS-800
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API, JSPUI, XMLUI
> Reporter: Claudia Jürgen
>
> At the moment the non-visibilty of metadata (for non-admins) is configurable
> in the dspace.dfg as
> metadata.hide.SCHEMA.ELEMENT.[QUALIFIER] = true
> This configuration based approached was intended to be an interim solution.
> Imo it would be better to add an attribute to the metadatafieldregistry
> similar to the internal flag for bitstreams.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
