New Dataset lowercases the name - breaks compatibility with all clients

[jaclu]

Most if not all clients have at least a few datasets with mixed case.
Currently such SipZips can't be uploaded into the intended dataset name if a sip zip is to be used on a new server

[hanswesterbeek]

I can see in the code that this is done intentionally so I am reluctant to simply change it without checking said intent.

Maybe @kiivihal know why it's there?

[hanswesterbeek]

@jaclu Can you provide me with a reproduction scenario for this?

What kind of error(s) do you see when you try to upload one?

[jaclu]

Almost all collections have datasets with mixed case names. If we have a server crash and need to recreate them, that would not be possible without changing collection name away from the name being used. With the test collection it seemed that if you named the dataset differently from what was expected you loose control over the records and it is impossible to unpublish a collection

[zemyatin]

It's the dataset "spec" that is used and must be in lowercase. Spec is for internal system use and thus lowercased, name is meant to be human readable. I'm not sure if those two are being interchanged here in the discussion, but I thought I would point it out.