You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #7135, the URLs were made unique in ExternalMediaLink (requested in #7134) such that if two ExternalMediaLinks had the same URL, it would display an error.
Here, a user wishes to use the same URL for two different ExternalMediaLinks, with different use-cases. The crux of the issue is that the URL points to a magazine, with many different pieces of content, so one uses it to introduce a tournament, and another uses it for an interview. The two ExternalMediaLinks therefore have different titles, different subject(s), and different subject organisation(s). But for any magazine in general, this could hypothetically cover multiple events. Or, really, any piece of media that has multiple "sub-pieces" of content.
The workaround I did was to add a slash to the end of the URL, making it unique, although this obviously depends on the web server re-routing the request correctly. (Other hacks like adding a fake anchor or HTTP GET parameter would work, but look ugly.)
Perhaps a more editor-friendly solution is to add chapter/section/page/etc. parameters, and derive uniqueness using this "compound key" instead.
The idea is that the same "sub-piece" of content would have a unique title, author, publisher, date, subject, subject organisation, and event, so having a duplicate of this would be an error.
On the other hand, it might be pretty easy to duplicate it anyway, with capitalisation/stylisation differences.
In #7135, the URLs were made unique in ExternalMediaLink (requested in #7134) such that if two ExternalMediaLinks had the same URL, it would display an error.
Here, a user wishes to use the same URL for two different ExternalMediaLinks, with different use-cases. The crux of the issue is that the URL points to a magazine, with many different pieces of content, so one uses it to introduce a tournament, and another uses it for an interview. The two ExternalMediaLinks therefore have different titles, different subject(s), and different subject organisation(s). But for any magazine in general, this could hypothetically cover multiple events. Or, really, any piece of media that has multiple "sub-pieces" of content.
The workaround I did was to add a slash to the end of the URL, making it unique, although this obviously depends on the web server re-routing the request correctly. (Other hacks like adding a fake anchor or HTTP GET parameter would work, but look ugly.)
Should this be a valid scenario to consider?