Link error to release 1.0.1

Hi!

Now when RC 1.0.2 has been added to the side menu on openEHR.org there
are two ways to get to version 1.0.1, the SVN one should not be used:

Specification Project
- Current Release <- This link is correct. (/releases/1.0.1/)
- Release 1.0.2 candidate (OK in SVN until release)
- Release 1.0.1 <- Wrong link target (in SVN)

The links to released specifications we want people to bookmark, cite
in papers/webpages and indexed by search engines should start with
http://www.openehr.org/releases/

Do you want correction requests like these to go to this mailinglist
or to webmaster@openehr.org?

Best regards,
Erik Sundvall
erisu@imt.liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-227579

Erik Sundvall wrote:

Hi!

Now when RC 1.0.2 has been added to the side menu on openEHR.org there
are two ways to get to version 1.0.1, the SVN one should not be used:

Specification Project
- Current Release <- This link is correct. (/releases/1.0.1/)
- Release 1.0.2 candidate (OK in SVN until release)
- Release 1.0.1 <- Wrong link target (in SVN)

The links to released specifications we want people to bookmark, cite
in papers/webpages and indexed by search engines should start with
http://www.openehr.org/releases/
  
fixed for 1.0.1 and 1.0; 0.95 and 0.9 don't seem to work for some reason
- the mapping rule may not work due to the target .html page being named
differently...unless anyone thinks this matters, I will probbaly leave
it (I thought I could fix it by committing copies of the index.html etc
under the name roadmap.html, but this doesn't work), unless Anthony can
see why this doesn't work.
Do you want correction requests like these to go to this mailinglist
or to webmaster@openehr.org?
  
this is fine at the moment - better as there are a few of us here with
write access.

thanks

- thomas

Hi,

Thomas Beale wrote:

Erik Sundvall wrote:

Hi!

Now when RC 1.0.2 has been added to the side menu on openEHR.org there
are two ways to get to version 1.0.1, the SVN one should not be used:

Specification Project
- Current Release <- This link is correct. (/releases/1.0.1/)
- Release 1.0.2 candidate (OK in SVN until release)
- Release 1.0.1 <- Wrong link target (in SVN)

The links to released specifications we want people to bookmark, cite
in papers/webpages and indexed by search engines should start with
http://www.openehr.org/releases/
  
fixed for 1.0.1 and 1.0; 0.95 and 0.9 don't seem to work for some reason
- the mapping rule may not work due to the target .html page being named
differently...unless anyone thinks this matters, I will probbaly leave
it (I thought I could fix it by committing copies of the index.html etc
under the name roadmap.html, but this doesn't work), unless Anthony can
see why this doesn't work.

The mappings only work for the root paths, the version numbers shouldn't
make any difference at all.

Can you let me know what the exact URLs that should work are?

Hi Anthony,

URLs that work:
http://www.openehr.org/releases/1.0.1/roadmap.html
http://www.openehr.org/releases/1.0/roadmap.html

URLs that should work the same way, but don't....
http://www.openehr.org/releases/0.95/roadmap.html
http://www.openehr.org/releases/0.9/roadmap.html

AFAIK, the mapping rule is as follows:

http://www.openehr.org/releases/$ver/$doc ->
http://www.openehr.org/svn/specification/TAGS/Release-$ver/publishing/$doc

not sure what can be happening.... could the $ver pattern be a regex
match expecting a leading non-zero digit?

thanks

- thomas

Hi Tom,

Thomas Beale wrote:

Hi Anthony,

URLs that work:
http://www.openehr.org/releases/1.0.1/roadmap.html
http://www.openehr.org/releases/1.0/roadmap.html

URLs that should work the same way, but don't....
http://www.openehr.org/releases/0.95/roadmap.html
http://www.openehr.org/releases/0.9/roadmap.html

AFAIK, the mapping rule is as follows:

http://www.openehr.org/releases/$ver/$doc ->
http://www.openehr.org/svn/specification/TAGS/Release-$ver/publishing/$doc

The web server does not do any mapping for /releases URLs.

On the file system the /releases directory is a real directory in the
web tree.

There is a README file in that directory that mentions what you need to
do to 'publish' a release to that directory, which reads:

"to create a new release area from subversion, use a command like

svn export
http://www.openehr.org/svn/specification/TAGS/Release-N.N.N/publishing N.N.N

from this directory"

Looks to me as if those releases have not been published.

Good, that's fits what I remembered from previous discussions, and I
believe that this is a very good approach making the releases
available no matter what happens to uptime or load on the subversion
installation. It will also be easy to keep these (releases/) urls
if/when changing systems in the future.

The only thing I think is missing now is to make the directory listing
visible in this directory and it's subdirectories. I know some
disagree to having visible directory listings, but the specification
documents are _very_ central to openEHR and even URL-hackers should
have an easy way to tell that there are newer or older releases and
comfortable alternative ways to SVN if they want to download the a
whole release.

Please make an exception and turn on the index listing for this
directory. (And if possible also for the directory
http://www.openehr.org/publications/ and its subdirectories.) Only
people tinkering with the URL in the browser will see these listings,
not the average user so the plain Apache autogenerated lists will do
just fine, please just turn them on for these directories.

I think URLs containing the releases/ and publications/ ar the ones
currently most likeky to be cited in papers etc.and thus need to be
permanent.

// Erik

Anthony Peacock wrote:

The web server does not do any mapping for /releases URLs.

On the file system the /releases directory is a real directory in the
web tree.

There is a README file in that directory that mentions what you need to
do to 'publish' a release to that directory, which reads:

"to create a new release area from subversion, use a command like

svn export
http://www.openehr.org/svn/specification/TAGS/Release-N.N.N/publishing N.N.N

from this directory"

Looks to me as if those releases have not been published.
  
aha.....didn't think of looking for a real directory! Now it all makes
sense....can fix it myself then...

- thomas

All,

the release links now are correct and serving pages properly for all
releases. Re Erik's other request, the $OPENEHR/www/releases and
$OPENEHR/www/publications directories seem like safe candidates to me
for turning on the directory listing.

- thomas

Erik Sundvall wrote:

Hi,

Thomas Beale wrote:

All,

the release links now are correct and serving pages properly for all
releases. Re Erik's other request, the $OPENEHR/www/releases and
$OPENEHR/www/publications directories seem like safe candidates to me
for turning on the directory listing.

I have turned on the directory listings for those two URLs.