|Anonymous | Login | Signup for a new account||2013-12-11 06:34 EST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0001968||[Slicer4] Core: Documentation & Wiki||minor||have not tried||2012-05-01 18:50||2013-06-14 23:34|
|Summary||0001968: Setup robot.txt so that only current stable version of Slicer documentation is indexed|
See http://www.mediawiki.org/wiki/Manual:Robots.txt [^]
The following pages should be excluded:
May be documentation associated with slicer 3.6, 3.5 etc .. should also be excluded ?
From Greg Sharp - april 12th 2012:
I just noticed today, when I use a common, commercial search
engine to find the Slicer documentation, the pages for
version 4.0 appeared higher in the list than documentation
for version 4.1. This caused me to refer to an old version
of the documentation.
Of course ok for me, but I think it can be confusing for
new users to get the old documentation.
|Tags||No tags attached.|
Could also use the magic word __NOINDEX__
See http://www.mediawiki.org/wiki/Help:Magic_words [^]
I don't think "unindexing" content is the best solution here.
First, disabling crawling doesn't clear the index. It take a long time for that information to expire.
Second, that content may still be useful to someone. That's especially true of the 3.X documentation.
Third, I'd like to see what the best practices are. For instance, I get old versions of the VTK docs all the time when I do a search. Same for python sometimes. That's not great, but it is predictable and understandable behavior.
The alternative fixes are to
1) provide pointers to the most current documents at the top of the 4.0 pages (that's what W3C standards do -- always maintain a "latest" pointer)
2) Have a "latest" version on the wiki that redirects or is copied in some way,
3) Have documents that describe current behavior as well as recent changes (for example, the python docs say "since version 2.6" or "added in 2.5").
|Good point. Will think about it. Assigned the issue back to me.|
From Lauren - May 3, 2012:
you could do what NIH does for old grant info pages, or what amazon does so that people know the model number is old, edit the top of the page with info pointing to the current version
or have wiki URLS that point to Current, and redo those links when the latest stable version changes, maybe they will accumulate more google cred since they are longer lasting URLs
my 2 cents
|Closing the issue because the approach used in 0002887 achieves the same purpose.|
Reminder sent to: gregsharp
Hi Greg, I believe the confusion between different version of the documentation has been removed. For details, see 0002887.
Let me know what you think.
|2012-05-01 18:50||jcfr||New Issue|
|2012-05-01 18:50||jcfr||Status||new => assigned|
|2012-05-01 18:50||jcfr||Assigned To||=> jcfr|
|2012-05-01 18:50||jcfr||Assigned To||jcfr => mhalle|
|2012-05-01 19:19||jcfr||Note Added: 0004119|
|2012-05-01 23:53||mhalle||Note Added: 0004120|
|2012-05-02 10:51||jcfr||Assigned To||mhalle => jcfr|
|2012-05-02 10:52||jcfr||Note Added: 0004124|
|2012-05-03 18:11||jcfr||Note Added: 0004156|
|2012-05-15 18:56||jcfr||Category||Slicer Wiki => Documentation & Wiki|
|2012-08-21 15:59||jcfr||Target Version||=> Slicer 4.3.0|
|2013-06-14 23:31||jcfr||Relationship added||related to 0002887|
|2013-06-14 23:31||jcfr||Relationship added||related to 0002905|
|2013-06-14 23:32||jcfr||Note Added: 0008774|
|2013-06-14 23:32||jcfr||Status||assigned => resolved|
|2013-06-14 23:32||jcfr||Fixed in Version||=> Slicer 4.3.0|
|2013-06-14 23:32||jcfr||Resolution||open => fixed|
|2013-06-14 23:34||jcfr||Issue Monitored: gregsharp|
|2013-06-14 23:34||jcfr||Note Added: 0008775|
|Mantis 1.1.4[^] Copyright © 2000 - 2008 Mantis Group|