The reason the page was dead on Friday was that EE's JPS code got confused by a topic name containing a slash. It thought Applications >> Email >> Lotus Notes/Domino, having a slash in the name, should link to a URL of /Applications/Email/Lotus_
no, but when that URL was received, it interpreted it to mean, "there is a main topic of Applications, containing a subtopic of email, containing a further subtopic of Lotus Notes, which contains a final topic of Domino. The last two were not true, the "further" subtopic SHOUDL HAVE BEEN the "final" one named "Lotus Notes/Domino." Apparently, the crack (CRAK?) EE team reprogrammed the URL generator so slashes area treated teh same as spaces, and gen a RUL with an underscore, and the TA of Lotus_Notes_Domino is recignized prperly.
And of course, there is also a new TA of "Web Development >> Lotus Domino Admin." That makes very little sense, admin if anything belongs closer to Email or App Servers than Web Develoment. In fact, "Ap Servers >> Lotus Notes/Domino" is an alias for this TA of "Applications >> Email >> Lotus Notes/Domino."
I've actually proposed a more logical arrangement, I think, that accounts for navagability, topic groupings, hierarchy levels, and content activity. See http:Q_20958332.html
). The basic idea?
- Use aliases in the Web Dev, Web Servers, App Servers, and Email topics.
- Place a Lotus TA in the Applications main TA
- Lotus TA contains SmartSuite and Notes-Domino
- Notes-Domino TA is organized by Admin, Dev, and User questions
Please respond there with your thoughts!