Interesting... It looks like the number of records has updated itself since yesterday. Perhaps the automatic database migration is working, just slowly. I'll watch it.
On Wednesday, March 7, 2018 at 3:17:03 PM UTC-9, wlruth...@alaska.edu wrote: > > > While upgrading our repository we initially built DSpace-6.0 but it was > unable to fully ingest > the legacy postgres database used by the older DSpace-3.1 system. We were > told we'd need > to first install DSpace-3.x, upgrade that to DSpace-5.x, then upgrade to > DSpace-6.0. > > So we built a DSpace-3.6 system and it was able to read the DSpace-3.1 > database. We then > built a DSpace-5.5 system with a copy of the entire database. All seemed > well at first but on > closer inspection it's doing the same thing as our original DSpace-6.0 > system - ignoring most > of the database. The manual says DSpace will automatically fix the > database or that the > 'dspace database migrate' command will accomplish this. Neither seems to > have had any > effect. I'm scanning through logfiles to see if it silently told me that > something went wrong. > > I know other DSpace users have successfully upgraded from DSpace-3.x to > DSpace-6.0 so > that's encouraging. Am I missing a step? Do I have install DSpace-4.x > before DSpace-5.x? > > Thank you for any help you can provide. > > > > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
