Thanks for the quick answers! I'd like to be able to get all the DC metadata into the DC datastream because, well, that's where it SHOULD be. :-) Also, if I need some of it there but more of it elsewhere, I'll have to duplicate it. And then I'm also integrating with Solr via GSearch, and it'd be nice if it all came in on one datastream. Oh, and part of the grant we're doing work on involves exchanging objects via ORE between Fedora and another product. So, overall, I just see a lot of reasons why sticking to the recommended manner of packaging FQDC in the DC datastream would be the elegant solution.
Anyway, a few mods to two classes (DCField and DCFields) managed to carry the following from a FOXML doc ingest through dissemination of the DC datastream: <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"; xmlns:dc="http://purl.org/dc/elements/1.1/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:cuir="http://clemson.edu/cuir/"; xmlns:dcterms="http://purl.org/dc/terms/"; xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd http://purl.org/dc/terms/ http://dublincore.org/schemas/xmls/qdc/dcterms.xsd";> <dc:title>This is the title</dc:title> <dc:creator>Test Program</dc:creator> <dc:description>A test object</dc:description> <dc:publisher>Scott</dc:publisher> <dc:date>2011-06-30T14:00:00.001Z</dc:date> <dc:type>text</dc:type> <dc:identifier>test:pid00b</dc:identifier> <dc:rights cuir:type="string" xsi:type="dcterms:accessRights">possession 9/10</dc:rights> <dcterms:temporal xsi:type="dcterms:period">name=The Great Depression; start=1929; end=1939;</dcterms:temporal> </oai_dc:dc> without any immediately obvious ill-effects elsewhere. Can't use Fedora's search on the "temporal" property (not even a database column for it), but then I'm relying on Solr for searches anyway. Modifications so far don't seem to touch anything utilized to maintain the triple store (I *think* because that part relies on a map of elements to index, and I don't add the additional one to the map). However, wouldn't it be cool if .... ;-) That's this afternoon's spike. The degree to which I actually customize a build (if at all) for deployment depends a lot on whether any of this is on the development roadmap. What I've done thus far is OK. If I have to do more in other classes, I might tip the balance. Anyway, thanks again for the information! Scott On 07/12/2011 11:47 AM, aj...@virginia.edu wrote: > The original intention of the DC datastream was purely to support very basic > repository administration, and the "traditional" answer to questions about > the advanced use of DC has been, as Ben did, to suggest that a new datastream > be created (which would then be able to support arbitrarily complex XML). DC, > as a datastream, has always been an absolutely lowest common denominator for > object metadata. > > In addition to Ben's point about 3.x-series repositories, there is the fact > that the Resource Index pulls RDF triples from DC and expanding the range of > content that might be found therein would have some interesting knock-on > effects on that process. > > --- > A. Soroka > Online Library Environment > the University of Virginia Library > > > > > On Jul 12, 2011, at 11:28 AM, Scott Hammel wrote: > >> Hi, >> >> Are there plans to support any of the following for Dublin Core content >> on the DC datastream? >> - retaining attributes present on XML elements during ingest >> - adding the dcterms namespace >> - supporting use of dcterms as properties in addition to the legacy dc >> elements >> - supporting use of additional namespaces and embedded XML in the DC >> datastream >> >> I am currently adding minimal support for these to a customized build of >> Fedora. I'm trying to decide how thorough I need to be :-) -- that is, >> will I need to maintain the customizations indefinitely or is support >> for these on the roadmap (I can't find a current one on the Fedora >> Commons websites). >> >> Thanks, >> Scott >> >> -- >> CCIT >> Clemson University >> 864-656-8118 >> >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Fedora-commons-users mailing list >> Fedora-commons-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > -- CCIT Clemson University 864-656-8118 ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
