-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
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
Unable to change Authority Record slug #1006
Comments
Hi @rferris ! Thanks so much for sharing this idea. While we would love to see a method for end users to easily update authority record slugs to AtoM's user interface, at this time, I'm not sure this is a solution we will implement. Changing the permalink of a resource in AtoM without the user explicitly choosing to do so could have unexpected consequences - for example, breaking every external link added to third-party websites. Long term, our preferred solution would be to add support for a Rename module for authority records, similar to what we've added for descriptions, as described in our docs here: If you are curious to see the code behind this, here are some of the main files used:
I'll leave this issue open for now, to make it easier for others to find your code snippet in case they would like to implement this locally. Cheers, Dan Gillean, MAS, MLIS |
Hi Dan, Agreed - my quick fix here definitely isn't ideal. I'll see if I can get time to create a rename form and if I can I'll do a pull request on it. :) Cheers, |
Fix merged in: #1542 |
Currently it is not possible to change the slug of an authority record once it has been created. Advice from Dan in the forum is to use SQL against the database directly to do this.
Regenerating slugs
In order to avoid this I modified the QubitActor.php file as per the following diff:
This allows a user to simply edit the record, change the title, hit save, and have the slug change accordingly. As far as I can tell this is effectively no different to doing this via SQL and the CLI slug utility. Whether it's the way the team at Artefactual would go about this or not, I'm not sure. I did, however, want to provide my change for your consideration.
The text was updated successfully, but these errors were encountered: