What, you mean like this? :)
http://sourceforge.net/mailarchive/forum.php?thread_name=20070424182230.GA28212%40pomona.hpl.hp.comforum_name=dspace-devel
On 27 January 2014 12:09, helix84 heli...@centrum.sk wrote:
How about before voting we first try to find out the reasons why it
was
@lists.sourceforge.net
Subject: Re: [Dspace-devel] Should we simply un-deprecate DCValue?
Hmmm I'm not going to vote, because I do believe that DCValue needs to go.
We have structures for MetadataValue which (iirc) were put in place when we
allowed multiple metadata schemas to be registered
There was some discussion on #dspace this morning. It's been attached
to the Jira issue.
https://jira.duraspace.org/browse/DS-1883
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital
Well, we could immediately (or very soon) do something in 5.0 (=master
branch) so that this issue doesn't run down again and sleep through
yet another major release. Whatever we are going to do, I would
suggest beginning quickly so that it gets done.
--
Mark H. Wood, Lead System Programmer
Hmmm I'm not going to vote, because I do believe that DCValue needs to
go.
We have structures for MetadataValue which (iirc) were put in place when we
allowed multiple metadata schemas to be registered. It's wrong to have
things lying around that suggest they are Dublin Core, when they
Continuing in the things that bug Mark no end vein
DCValue has been @Deprecated for ages, but it's still used all over
and I don't readily see why it is deprecated. The class was created
in 2002, gained a 'schema' member in 2005, and then was deprecated in
2007. Why?
We seem to have a
+1
IMHO it really shouldn't be deprecated as we never have had a formal
plan to replace it. Once a formal plan is in place, and we've taken
steps towards implementing that plan, we can re-deprecate it if needed.
On 1/24/2014 2:58 PM, Mark H. Wood wrote:
Continuing in the things that bug Mark
+1
--Hardy
On 1/24/14 3:50 PM, Tim Donohue tdono...@duraspace.org wrote:
+1
IMHO it really shouldn't be deprecated as we never have had a formal
plan to replace it. Once a formal plan is in place, and we've taken
steps towards implementing that plan, we can re-deprecate it if needed.
On
