Brian:
It was for bitstream ".avi" which for some reason was missing from my Bitstream
registry. I was sure I had it in my previous version (I have a lot of records
with AVI Videos), but I remember doing an extensive rebuild of the bistream
registry when I upgraded and I probably accidentally left it out.
Every bitstream with an ".avi" suffix is an ID: "1" unknown. I already found
all of the bistreams (and items) that have the ".avi" suffix through SQL. My
next step is to look for all of the bitstreams that have an ID of "1", and
separate out all of the ones which are not ".avi" before doing a global change.
Thanks, again, for your advice.
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CULIT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
________________________________
From: Brian Freels-Stendel [[email protected]]
Sent: Thursday, March 07, 2013 4:46 PM
To: George S Kozak; [email protected]
Subject: RE: Question about bitstream format registry
Oh, bother.
Both of those solutions would require that the ID be the old format ID. I’m
kind of counting on that, to be honest. If the ID changed to the “Unknown”
format, you could try putting all of the relevant bitstream IDs into an update
like “update bitstream set bitstream_format_id = [NEW_ID] where bitstream_id in
[BITSTREAM_ID_LIST(COMMA_SEPARATED)]”
B--
From: Brian Freels-Stendel [mailto:[email protected]]
Sent: Thursday, March 07, 2013 2:37 PM
To: George S Kozak; [email protected]
Subject: Re: [Dspace-tech] Question about bitstream format registry
Hi George,
Did the bitstream_format_id get changed to the “Unknown” type, or is it still
the original ID?
If it’s still the original ID, I would go into the database table
bitstreamformatregistry and change the ID of the new record to the old ID.
Then, of course, revert the ID of those few records you updated to the new ID.
If it’s not, I’d probably run a SQL query: “update bitstream set
bitstream_format_id = [NEW_ID] where bitstream_format_id = [OLD_ID]”
And for sure, make a backup of the db before trying either of these.
B--
From: George S Kozak [mailto:[email protected]]
Sent: Thursday, March 07, 2013 2:18 PM
To: [email protected]<mailto:[email protected]>
Subject: [Dspace-tech] Question about bitstream format registry
Hi…
I discovered today that I had a bitstream that was dropped from the bitstream
format registry (my fault) when I went from DSpace 1.7.1 to DSpace 1.8.2, so
every item using the specific bitstream now shows it as “unknown”.
I fixed things in the bitstream registry and fixed a few records by typing in
the correct ID number while the item is in “Edit” Mode, but I have 226 items to
be updated.
I was wondering if I did an index update would that automatically fix the
bitstreams to show that they are now known or is there some batch way to
updated the display of these bitstreams?
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
