Dear Mr. Palmer,
My opinion (as exemplified in WindMusic.org) is that DSpace "flat model"
is nice for most of us needing data models simple and manageable.
Authority Control (controlled vocabularies) is the door to control
LINKING of these simple flat records to other "objects"
(like Funder in this case). I call it the "Documentation Generic Data
Model": simple "flat" multilingual objects linked to others through
normalized "values" (codes).
Perfectly represented by DC + SKOS and some VoID for a perfect RDF soup!
WindMusic.org left MARC21 for a model made with those simple bricks.
My implementation of Authority Control allows those "links" to be
embedded within text, together with a prefix (for instance kind of
contribution of an author)
or a prefix (number of instrument needed to play a music score).
DSpace community choose a more "database oriented" solution (a separate
field for the code), but it could be suitable also:
1) Create a specialized Authority Plugin for Funders+Grants (some
pluggable java code!)
2) Store the Funder code in the Authority Code part of the DSpace Field
3) Store the Grants numbers, separated with commas or semicolons, in the
DSpace Field Text Value
4) Improve DSpace Authority Plugin Interface so a plugin could:
a) Add to Lucene Index the different names for the Funder
b) Display the Funder Name and not its code, based on user language
(chinese, english...) followed by the grand codes (semicolons replaced
by line breaks)
This may require to enrich the current Authority Plugin Interface
(support of synonyms for indexation + support of translations for display)
The ASKOSI.org Authority Control Plugin would also greatly benefit from
improvement to DSpace Authority Plugin Interface.
Hope this helps!
Twitter @ChristopheDupri or
Le 29/01/2013 10:43, David Palmer a écrit :
> We want to show funder data in the publication records in DSpace. On one
> record, there could be multiple grant names from the same funder, two or
> more funders on the same publication, two or more grant numbers, etc. If we
> have 4 separate DC fields for,
> Grant Name
> Grant number
> DC metadata then cannot show which grant name belongs to which funder, which
> grant number belongs to which grant name, etc.
> Give up on DC metadata for this? We made this record showing our intent.
> It uses a control number to look up data on an outside table holding the
> data, bringing the data into the DSpace publication item on-the-fly.
> [scroll to bottom]
> Is there a way to do this better?
> David Palmer
> Associate University Librarian
> The University of Hong Kong Libraries
> 10/F, Kennedy Town Centre
> 23 Belcher's Street
> Kennedy Town
> Hong Kong
> tel. +852 3921 2921
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> Dspace-general mailing list