It is really much better to create your own datastream for metadata that you want to use externally. I wish we had called the DC datastream "repoMeta" or something. It was just intended to be the base metadata needed for the repository manager to be able to function and was not intended to be exposed externally. We just used Dublin core because it was as close to a basic schema as we could get at the time. The "basic search" that is built-in was only intended to be a management tool.
It would also be better not to use an in-line datastream for any metadata datastream, as a general rule. If your FOXML files get larger than 20-30 K it can affect performance for most applications. Metadata records can really bulk up that file pretty quickly if you are not careful. Use a managed content datastream, and use any kind of metadata you like. ____________________________________ Thornton Staples Director of Community Strategy and Alliances Director of the Fedora Project DuraSpace, Inc. [email protected] (202) 684-6952 skype: thorny.staples www.duraspace.org On 4/24/10 2:53 PM, Walker Sampson wrote: > Hi all, > > I have been migrating some old records from MySQL to Fedora, and have > been using some of the newer DC terms available since December 2006 in > the "dcterms" namespace: http://purl.org/dc/terms/. > > It seems the compulsory DC datastream defaults to the "dc" namespace > (http://purl.org/dc/elements/1.1/). I went ahead and changed this in > my FOXML files to the newer one, hoping it might add support for new > terms like "alternative", "extent" and so on. > > Upon ingestion however it looks like only those terms which are also > in the legacy namespace come through, and the > "http://purl.org/dc/terms/"; value gets replaced with the > "http://purl.org/dc/elements/1.1/"; value. I assume then that Fedora > doesn't support the new terms in its DC datastream. If so, has there > been a statement on when this might come to pass? Or does anyone know > a way to have these elements shown in the DC datastream after ingest? > > Assuming Fedora isn't going to work with these elements on this > release, my solution will be to add in a custom inline datastream > holding these values for me. > > Anyone had experience with this issue? > > Thanks- > Walker > > ------------------------------------------------------------------------------ > _______________________________________________ > Fedora-commons-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > ------------------------------------------------------------------------------ _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
