(by clicking on the url, going to the number, and replacing two
characters). This is somewhat cumbersome (especially after the first dozen
of changes in urls. Suggestion:
(1) Would it make sense to include other versions of the document as urls
on the page? See, e.g., the following documentation of postgres, where each
page has a pointer to the same page in different versions:
Re: versions of documentation: suggestion for improvement
There's been some discussion along the lines of doing some things like
what you propose which were spun out of discussion in SOLR-10595 into the
issue LUCENE-7924 ... but so far no one has attempted the
tooling/scripting work needed to make it happen.
Thanks for the prompt answer and the links. I see there's quite some
interesting discussions around the issue already. Let me take some time to
get into details.
I also noticed that there's the concept of "latest" (similar to "current"
in postgres documentation) in solr. This is pretty cool. I am afraid
though, that this currently is somewhat confusing. E.g., if I search for
managed schema in google I get this as 1st url:
i'm not sure where you got the impression that *replacing* a version
number with "/latest" in the URL was designed to work ... the redirects
are setup so that if you *remove* the version number, the rest of the path
will redirect to the current version.