Access to package document disappears for collaborators if owner renames document

[gkamener]

If a package owner renames a package document after collaborators have accepted a collaboration invite, the package will no longer be visible to the collaborators.

To replicate the issue:

1. Package document owner invites collaborator
2. Collaborator accepts invite
3. Package owner renames package document
4. Collaborator no longer sees the package on their Collaborate page

Workaround:
5. Owner must send new invite to collaborator to accept before they can regain access to the package document

[sformel]

Ran into this today. Not sure if this is what breaks the collaboration permissions, but I was surprised that the URL for the document is tied to it's title instead of a UUID. Would it be possible to mint an identifier for each package document, form which the URL is generated, instead of being tied to the title?

[jon-ide]

The document in ezEML is just a file in the ezEML server's file system. It must be identified somehow. It would be possible to create a database that maps UUIDs to filenames and thereby introduce a level of indirection. This would necessitate intercepting document renaming and updating the database when renaming happens.

We may consider making such a change at some point. Document renaming is uncommon, however. Unlike the document Title, which shows up in the published metadata. the document name that's chosen when the document is created is relevant only within ezEML.

Thank you for the suggestion!

[sformel]

Got it. I forgot I had renamed my test in two places (title and document name), which is why the URL changed. I see your point that it's a fair bit of work to implement an identifier-based system, and I can be content with the current system.