-
Defect
-
Resolution: Cannot Reproduce
-
Major
-
None
-
None
-
None
-
2
There may have been an Atom feed change or regression in the 2.0 ACADIS production system.
It is unclear if this issue relates to the OAI repo or the Atom Feed.
Initial notes follow:
There are two issues I've found so far, slightly different:
>
>1) The "entry" elements no longer have any "<link>" tags. Before, most
>of them had a <link> tag with an attribute rel="enclosure". Now, none
>of the entry elements seems to have a <link> tag (or even the
>genericLink tag that was GI-cat specific).
>
>2) The "id" element of each <entry> used to be in UUID format. Now they
>all seem to be in 1.1.1.1 format (with varying numbers). This is not a
>valid Atom ID, and thus the resulting feed is not Atom or OpenSearch
>compliant anymore. The ID is supposed to be a URI, and so if a UUID is
>used, it should look something like this:
>
>urn:uuid:f6e75581-e0bc-4f64-8f48-a86afe04bf30
>
>Just the UUID value (f6e75581-e0bc-4f64-8f48-a86afe04bf30) is still not
>compliant, it needs some sort of domain-ish stuff. (I had put this in
>my original notes, and hadn't really checked since the Italians updated
>to see if they'd corrected this specific issue. I don't remember what
>the UUID's looked like exactly yesterday to remember if it was correct
>or not, but it's definitely not correct now).
>
>I hope this helps.
It is unclear if this issue relates to the OAI repo or the Atom Feed.
Initial notes follow:
There are two issues I've found so far, slightly different:
>
>1) The "entry" elements no longer have any "<link>" tags. Before, most
>of them had a <link> tag with an attribute rel="enclosure". Now, none
>of the entry elements seems to have a <link> tag (or even the
>genericLink tag that was GI-cat specific).
>
>2) The "id" element of each <entry> used to be in UUID format. Now they
>all seem to be in 1.1.1.1 format (with varying numbers). This is not a
>valid Atom ID, and thus the resulting feed is not Atom or OpenSearch
>compliant anymore. The ID is supposed to be a URI, and so if a UUID is
>used, it should look something like this:
>
>urn:uuid:f6e75581-e0bc-4f64-8f48-a86afe04bf30
>
>Just the UUID value (f6e75581-e0bc-4f64-8f48-a86afe04bf30) is still not
>compliant, it needs some sort of domain-ish stuff. (I had put this in
>my original notes, and hadn't really checked since the Italians updated
>to see if they'd corrected this specific issue. I don't remember what
>the UUID's looked like exactly yesterday to remember if it was correct
>or not, but it's definitely not correct now).
>
>I hope this helps.