Skip to content
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

redirect old language URL to language index page #11

Open
xrotwang opened this issue Aug 25, 2016 · 10 comments
Open

redirect old language URL to language index page #11

xrotwang opened this issue Aug 25, 2016 · 10 comments

Comments

@xrotwang
Copy link
Member

If we switch to relating inventories to Glottolog languoids (dialects and languages), we must switch the vafriety identifiers to Glottocodes, thus breaking the old variety URLs. Since varieties have not been considered core resources of PHOIBLE Online, it seems best to redirect the old URLs to the languages index page, rather than returning HTTP 410 (which would be more semantically correct).

@drammock
Copy link

So the idea is that the content for Aja (Benin) at http://phoible.org/languages/ajg would move to http://phoible.org/languages/ajab1235, and the old URL would redirect to the languages index page?

I realize that in some cases one ISO 639-3 based URL may correspond to multiple new Glottocode-based URLs... so in that case is it possible for old ISO-based URLs to automatically return search results for that code? So if ISO code xxx corresponds to glottocodes yyyy1234 and zzzz5678, then the URL phoible.org/languages/xxx would return a page with links to the yyyy1234 and zzzz5678 pages. Is that easy? hard? undesirable for some reason I don't recognize?

@xrotwang
Copy link
Member Author

Redirecting to a page listing all languages mapped to a given ISO code should be possible.

@drammock
Copy link

Great, thanks @xrotwang. @bambooforest any opinion here?

@bambooforest
Copy link
Member

I think this solution sounds good.

@xrotwang
Copy link
Member Author

Just tried to implement this redirection, but would like to avoid the intermediate page listing possible new matches for simplicity. This would mean the following ISO codes don't have a matching new language (the ones prefixed with --- have no match, the other ones have multiple matches; so 22 out of 1,672 would end up with HTTP 410):

+++ izi {'izii1239', 'ikwo1238'}
--- ori
--- jar
--- adc
+++ kjn {'oyka1239', 'kunj1245'}
--- noo
--- nbf
--- dap
--- gio
--- gny
--- baz
--- qpt
--- psx
+++ sgw {'chah1248', 'seba1251', 'ezha1238'}
--- xuu
--- bsc
+++ gup {'guma1252', 'naia1238', 'gunw1252', 'mura1269', 'gune1238'}
--- stc
--- yrm
--- gmo
+++ din {'dink1262', 'sout2832', 'nort2815'}
+++ nyf {'kamb1298', 'kaum1238'}

acceptable?

@xrotwang
Copy link
Member Author

ping @bambooforest

@bambooforest
Copy link
Member

@xrotwang we definitely updated some of the ISO codes given their changes

@xrotwang
Copy link
Member Author

So given that there are also changes, I'd say we can live with breaking 22 URLs - of pages which are not representing core data of PHOIBLE, but rather serve as navigation.

@drammock
Copy link

breaking 22 URLs is OK with me, but note that some of these could be redirected (the ones where there is only one glottocode in PHOIBLE that matches the current ISO codes that replaced the missing one). Examples (not a complete list):

  • ori changed from language to macrolanguage, with constituent members Oriya ory and Sambalpuri spv. Only ory is in PHOIBLE (oriy1255)
  • noo split into dtd and nuk. Only nuk is in PHOIBLE (nuuc1236)
  • dap split into tgj and njz. Only njz is in PHOIBLE (nyis1236)
  • gio split into several new ISO codes, but of them only gqu is in PHOIBLE (qaua1234)

Others cannot be redirected easily, e.g.:

  • nbf split into nxq and nru. PHOIBLE has one of each (naxi1245=nxq, yong1270=nru) so no obvious redirect choice here.

Is it worth it to go through the remaining ones one by one to determine if a single redirect target makes sense? (note: even if we do this, I'm viewing it as a deprecation cycle; those URLs should go dead after the next release)

@xrotwang
Copy link
Member Author

Yes, we can go through these one by hand. I'll leave the issue open. Once we've gone through the list, the glottocode we'd like to redirect to can go in this JSON - from where I can pick them up when running a DB update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants