Page History

...

However, this redirection implies additional overhead. Pages local to VIVO calculated the alias URL and used it as the "src" property on the image, avoiding the redirection. But because the "alias URL" was not present in the RDF, it was not available to external applications, which resulted in excessive load times for pages that displayed dozens of images.

In VIVO release 1.2 we added the "The directDownloadUrl" property to of FileByteStream objects . This property contains the "alias URL", is created when the image is ingested, and is used both by VIVO and by external applications when displaying images.VIVO releases from 1.2 through 1.4.1 contained code that would analyze the data model at startup, creating this property in the RDF if it was not present. Starting with release 1.5, that code has been removed, and ingested RDF for image files must contain the "directDownloadUrl" property in addition to those described above.

Accordingly, the FileByteStream examples shown above must now look like this instead:

...