Opened 3 years ago
Last modified 3 years ago
#1047 new defect
indico URLs - keep confId in front, keep parameter order
| Reported by: | arescope | Owned by: | |
|---|---|---|---|
| Priority: | very low | Milestone: | v2.3 |
| Component: | General | Version: | |
| Keywords: | Cc: |
Description
currently INDICO URLs seem to put the most discriminative element first in the parameter list of the URL, i.e
https://indico.cern.ch/conferenceDisplay.py?confId=152323 = event URL
https://indico.cern.ch/materialDisplay.py?materialId=minutes&confId=152323 = URL for minutes, confId gets pushed to back
similar
http://indico.cern.ch/conferenceTimeTable.py?confId=149557#20120521 == CHEP2012
https://indico.cern.ch/abstractDisplay.py?abstractId=489&confId=149557 == one abstract in CHEP2012, again confId at end
It looks like browsers such as chrome will use longest-match on the URL in order to group related pages and keep track of "most often accessed". The current INDICO URL style does not work well in this case. Could I suggest to reorder the parameters so that the most significatn (i.e confId) is kept at front? Similarly, if there is some other "hierarchy" (conf->talk->material->file1,file2,.. ?), suggest to keep the parameters ordered by most-significant first.
Change History (1)
comment:1 Changed 3 years ago by jbenito
- Milestone changed from v1.0 to v1.5
- Priority changed from normal to very low
