#208 Synonyms for site names not working right?

[Lee Worden]

It looks like background jobs created on http://yushan.mcmaster.ca/theobio/somewiki are not visible on pages on http://lalashan.mcmaster.ca/theobio/somewiki. I would assume it's because $peURISynonyms either isn't working right, or isn't set right.

[Lee Worden]

Isn't used right in PEBackground*, it turns out.

Fixed in r992, I think.

[Lee Worden]

Actually I'm going to reopen this because while the visibility problem is fixed, there's one nuance still to take care of.

When we submit a job from yushan or lalashan, PE normalizes the project uri to say lalashan, not yushan, because we're using that as the standard form. When we search for a particular project, PE normalizes the search term to be based on lalashan, so it'll match the existing job data. So that works fine.

Then when PE finds a match, it returns the data to WW with project URIs based on lalashan. So if you're on lalashan, say on the "Sandbox" page, it'll search for the Sandbox project on lalashan, and when it comes back it'll recognize that it's found the Sandbox project on lalashan and report a match including project "Sandbox". When you load the same page on yushan, it searches for the Sandbox project on yushan; PE translates that to lalashan and finds the right jobs, but then WW sees the Sandbox project on lalashan and doesn't recognize that it's local because it's looking for a project on yushan. So instead of local project "Sandbox" it reports the full project URI, which is irritating and possibly confusing.

Solution: I guess after PE finds matching jobs, it should check the URIs against the original search terms and put them back in the form they were in in the request.

Unless I wanted to put the URI normalization in the WW side, before it sends requests, rather than having PE do it after receiving them.