Issue 11619

Technical BGBM BioCASE installation has wrong title, description and url

11619
Reporter: mdoering
Assignee: fmendez
Type: Bug
Summary: Technical BGBM BioCASE installation has wrong title, description and url
Priority: Critical
Resolution: WontFix
Status: Closed
Created: 2012-07-19 14:53:10.719
Updated: 2013-12-16 17:50:55.602
Resolved: 2012-10-17 12:25:10.788
        
Description: The PyWrapper for the BGBM is this:
http://jawa.gbif.org:8080/registry-ws/technical_installation/403a9f50-c065-11e1-9773-0024e8565763

With metadata like that:
"title":"BioCASe Installation",
"description":"BioCASe Access Point of AlgaTerra",
"homepage":"http://ww3.bgbm.org/biocase/pywrapper.cgi"

When it should be something like this, with "BGBM" being a substitute for the actual hosting organization name:
"title":"BioCASe Installation BGBM",
"description":"BioCASe installation BGBM",
"homepage":"http://ww3.bgbm.org/biocase/"
]]>
    


Author: fmendez@gbif.org
Created: 2012-07-19 15:14:26.218
Updated: 2012-07-19 15:14:26.218
        
Maybe we can improve the title and description, but the url is very hard to improve in the migration scripts, the url patterns we have are very different, for example: http://biocase.grinfo.net/pywrapper.cgi?dsa=SINGER, http://161.116.68.121/biocase/pywrapper.cgi?dsa=fungacat, http://141.20.245.232:55095/biocase2/pywrapper.cgi?dsa=BIODAT_ZFMK
So, the best thing i could do to infer a base url for technical installation was to get rid of the parameters, something like:
IF(INSTR(s.url,'?') > 0, SUBSTR(s.url,1,INSTR(s.url,'?') - 1),s.url) AS rooturl.
    


Author: mdoering@gbif.org
Comment: in those cases just the existence of pywrapper.cgi tells me you have to use the parent directory of that cgi script. That should be the case for all pywrapper installations, unless they have used some rewrites or virtual hosts which I remember 1 or 2 installations did use. But that is surely the exception
Created: 2012-07-19 15:31:37.186
Updated: 2012-07-19 15:31:37.186


Author: fmendez@gbif.org
Comment: This issue is related with the migration scripts and those changes can't be reverted now.
Created: 2012-10-17 12:25:10.812
Updated: 2012-10-17 12:25:10.812