DSpace 7 workflow_steps missing!

[Juan López]

Hi!

I've migrated a DSpace 6.3 to the 7.3 version, everything is working fine except for one thing: The collection table in my database doesn't have the columns workflow_step_1, workflow_step_2 and workflow_step_3.

I understand that the sql file V7.0_2021.10.04__alter_collection_table_drop_workflow_stem_columns.sql deletes this 3 columns, but, right now my DSpace doesn't have any user assigned to any rol.

I've run the migration of the database several times, but always get the same result, all my  previous roles assignments are missing.

¿Has anybody have the same issue? ¿Is there a way to fix this? 

Best regards,

Juan

[Tim Donohue]

Hi Juan,

Those columns no longer exist because they aren't used by DSpace 7 at all.  During the upgrade, all data in those columns should be migrated automatically.

Could you check your logs to see if an error is thrown when you run the migrations?  Also, can you verify that all your database migrations are listed as either "Success" or "Out of Order" (which means successful but run out of order) when you run "./dspace database info" from the commandline?

If any migrations are listed as failed or pending, then you need to run "./dspace database migrate ignored" again (as documented in the upgrade instructions) and check your dspace.log to see if any errors are occurring during that upgrade.

Please share what you find on this mailing list and we'll do our best to help.

Tim

---

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Juan López <juanlop...@gmail.com>
Sent: Thursday, August 4, 2022 11:43 AM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] DSpace 7 workflow_steps missing!

 

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/138bd110-6e61-479b-9ff5-c954c597a4ecn%40googlegroups.com.

[Juan López]

Hi Tim!

I ran into this post: https://groups.google.com/g/dspace-tech/c/enhTBvnQm68/m/WnEgFm2-AwAJ

and manually set the 5.7.2017.05.05 and 5.7.2017.04.11 to true with this:

insert into schema_version (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success) values (27,'5.7.2017.04.11','DS-3563 Index metadatavalue resource type id column','SQL','V5.7_2017.04.11__DS-3563_Index_metadatavalue_resource_type_id_column.sql',-1,'repositoryadmin','2022-08-04 17:45:08.793368',0,true);

insert into schema_version (installed_rank,version,description,type,script,checksum,installed_by,installed_on,execution_time,success) values (29,'5.7.2017.05.05','DS 3431 Add Policies for BasicWorkflow','JDBC','DS 3431 Add Policies for BasicWorkflow',-1,' repositoryadmin ','2022-08-04 17:45:08.793368',0,true);

after that, I did a "database repair" and then "database migrate ignored". It seems like everything is working as it should.

Thanks for the reply!

Juan.