Hi Alvin,
This is expected behavior (starting in DSpace 5) and is not a bug. As
of DSpace 5, *all objects* now use the Qualified Dublin Core schema that
comes with DSpace. Previously, you could only assign DC-based metadata
to Items. But, as of DSpace 5, Communities, Collections and Bitstreams
(i.e. Files) also use DC-based metadata. So, the fact that you see
files names in your "dc.title" field is expected behavior, as the
"dc.title" field is now used to store titles (i.e. names) of all
Communities/Collections/Items/Bitstreams.
This feature is noted in the "5.0 Release Notes" as "All objects now
have metadata support" (aka Metadata for All Objects). The reason for
this change was to enhance our data model to allow for (in the future)
capabilities to more easily add *new* custom metadata fields to any
object (again not just Items).
https://wiki.duraspace.org/display/DSDOC5x/Release+Notes
As for the database upgrade scripts, even though they are now run
automatically, you can still view them in the 5.x codebase at:
https://github.com/DSpace/DSpace/tree/dspace-5_x/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres
(They are numbered sequentially.. and any that start with "V5.0" are run
during the upgrade from 4.x to 5.0)
Hopefully that helps clarify what you are seeing after your 5.x upgrade!
Tim
On 6/30/2016 1:13 PM, Alvin Hutchinson wrote:
I have a problem that I think may be related to the upgrade from
version 4 to 5.
My database table, metadatavalue has a lot of filenames in the text
value where the metadata_field_id=64.
That field ID is normally reserved for title only so I wonder how
these filenames were recorded there.
There are also legitimate titles listed for the resource_id, but it
contains extraneous records with field ID 64.
Because upgrade no longer requires the user to execute a series of
scripts, I can no longer view the steps of what happens with the old
database to convert it to the new schema.
Has anyone else had or seen a similar problem?
Thanks in advance,
Alvin Hutchinson
Smithsonian Libraries
--
You received this message because you are subscribed to the Google
Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
You received this message because you are subscribed to the Google Groups "DSpace
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.
