search

HughP / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

category browsers broken on hosted demo #401

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
http://registry.oss-watch.ac.uk/categoryBrowser

click on any category and you get an 'internal server error'

Original issue reported on code.google.com by ste...@fullmeasure.co.uk on 3 Mar 2011 at 5:05

GoogleCodeExporter commented 9 years ago 
Why defunct? no reason give and surely not a dupe?

Original comment by ste...@fullmeasure.co.uk on 4 Mar 2011 at 1:51

GoogleCodeExporter commented 9 years ago 
Sorry Steve, that's too cryptic - what are you asking?

Original comment by ross.gardler on 4 Mar 2011 at 3:04

GoogleCodeExporter commented 9 years ago

Original comment by ross.gardler on 10 Mar 2011 at 12:28

GoogleCodeExporter commented 9 years ago 
There was a problem with most of the category data (Note there are other issues 
for category problems, eg. Issue 283, 413). 

Querying the data on registry.oss-watch.ac.uk revealed that all the categories 
that were broken had one simal:categoryId, for example : 

<http://www.jisc.ac.uk/whatwedo/themes/access_management.aspx> simal:categoryId 
"132246b7-6873-4708-96bc-0278780baa1c-per3648"

A few categories did work correctly, and these all had two simal:categoryIds 
assigned, for example:

<http://jisc.ac.uk/programme#62> simal:categoryId 
"132246b7-6873-4708-96bc-0278780baa1c-per3684" 
<http://jisc.ac.uk/programme#62> simal:categoryId "per3684"   

It turned out that the 'Internal error' was related to categories *not* having 
a simal:categoryId of the form "per1234".
I fixed this by putting in a project that posted along all the categories that 
were wrong and assigning them the correct simal:categoryId in the XML I posted. 

BTW, I like curl for this, I posted the attached file using this command:  

curl -v -d @LinkJISCProjects_xml.txt 
"http://registry.oss-watch.ac.uk/simal-rest/addProject"

Original comment by sander.v...@gmail.com on 6 Apr 2011 at 3:46

Attachments: