We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This mainly concerns already existing items and their migration.
The migration path should cover the following (maybe it does, in that case, this is just a reminder and a reference):
@@
;
The text was updated successfully, but these errors were encountered:
@kosarko Could be the solution to change separator in the crosswalks?
Sorry, something went wrong.
As one of the steps yes. The other should be replacing all the @@ in the database...
Btw does the v7 implementation sanitize the inputs so they don't contain ;?
@kosarko Could be the solution to change separator in the crosswalks? As one of the steps yes. The other should be replacing all the @@ in the database... Btw does the v7 implementation sanitize the inputs so they don't contain ;?
No, there is not such check for ; in the input. I will consider changing the separator string to @@, maybe it will be faster.
No branches or pull requests
This mainly concerns already existing items and their migration.
The migration path should cover the following (maybe it does, in that case, this is just a reminder and a reference):
@@
to;
) as mentioned in Upgrading the DSpace 7.2. to the CLARIN-DSpace 7.2. #1025 (comment)The text was updated successfully, but these errors were encountered: