+- AOP Forum (https://forum.aopwiki.org)
+-- Forum: AOP-Wiki Forum (https://forum.aopwiki.org/forumdisplay.php?fid=6)
+--- Forum: AOP-Wiki Technical Assistance (https://forum.aopwiki.org/forumdisplay.php?fid=8)
+--- Thread: <biological-organization-level> is not always visible in the rendered wiki page (/showthread.php?tid=191)
<biological-organization-level> is not always visible in the rendered wiki page - vasvir - 05 Apr 2022
Hi,
We noticed an inconsistency between the latest XML and some key events and maybe you could help us a bit to understand what's going on.
Case in point are events 1043, 1492, 1493 which have a non-empty <biological-organization-level> like Cellular or Tissue but it is not rendered in the wiki page.
In contrast, in the event 1847 that has the exact same value (Cellular) is visible.
There is a screenshot depicting the issue attached.
So why some in some key event <biological-organization-level> is rendered and in some it is not rendered?
Thanks in advance
Vassilis
RE: <biological-organization-level> is not always visible in the rendered wiki page - swedwards - 06 Apr 2022
This is scheduled to be fixed in the next couple of weeks. I will post here when the update has been deployed.
Steve
RE: <biological-organization-level> is not always visible in the rendered wiki page - vasvir - 08 Apr 2022
Thanks for the quick reply.
Good to hear that you will take care of it.
BTW a similar issue is that timestamps (creation-timestamp, last-modification-timestamp) are not exported in the KEs section of the XML.
They do exist for AOPs, KERs but not for KEs.
I double checked at the XSD and they are supposed to be exported also for KE.
Thanks again
RE: <biological-organization-level> is not always visible in the rendered wiki page - swedwards - 30 Apr 2022
The fix for this issue is scheduled to be deployed next weekend (May 7, 2022). If you have any questions after the update, please post them here.
RE: <biological-organization-level> is not always visible in the rendered wiki page - swedwards - 07 May 2022
Both of these issues have now been fixed. Let us know if you have any additional problems.