Closed milanmajchrak closed 1 year ago
Project type is loaded into Project name field:
Reason: It's because the local.sponsor metadata values are stored in different sequence in the CLARIN-DSpace5.x than in CLARIN-DSpace7.x.
local.sponsor
CLARIN-DSpace5.x sequence: <ORG>;<PROJECT_CODE>;<PROJECT_NAME>;<TYPE> CLARIN-DSpace7.x sequence: <TYPE>;<PROJECT_CODE>;<ORG>;<PROJECT_NAME>
<ORG>;<PROJECT_CODE>;<PROJECT_NAME>;<TYPE>
<TYPE>;<PROJECT_CODE>;<ORG>;<PROJECT_NAME>
I've tried to solve this issue in the FE, but then I realized it will be better to fix it during the migration. Original issue: https://github.com/dataquest-dev/dspace-angular/issues/232
Problem description
Project type is loaded into Project name field:
Reason: It's because the
local.sponsor
metadata values are stored in different sequence in the CLARIN-DSpace5.x than in CLARIN-DSpace7.x.CLARIN-DSpace5.x sequence:
<ORG>;<PROJECT_CODE>;<PROJECT_NAME>;<TYPE>
CLARIN-DSpace7.x sequence:<TYPE>;<PROJECT_CODE>;<ORG>;<PROJECT_NAME>
I've tried to solve this issue in the FE, but then I realized it will be better to fix it during the migration. Original issue: https://github.com/dataquest-dev/dspace-angular/issues/232