Home Forums Software ELAN Wishlist: relative file references for ECVs

Wishlist: relative file references for ECVs

This topic contains 2 replies, has 2 voices, and was last updated by  Matt Brown 1 month ago.

Viewing 3 posts - 1 through 3 (of 3 total)
Author Posts
Author Posts
January 16, 2019 at 17:36 #12603

Matt Brown

Hi there,

Matt from the BSL Corpus here, with a wishlist item …

In a perfect world where time and money were no object, it would be great if ECVs referenced as files worked in a similar way to media files, i.e. they had both an absolute and a relative reference.

The way I understand it, when you add media to an EAF, the XML tag contains two ways of referencing it: both as an absolute location and a relative one. This is very helpful when accessing EAFs from different computers on different operating systems with differently configured network shares. I’m guessing that if locating the media via the absolute reference fails, then it tries the relative one using the EAF’s location as the base?

ECVs, however, if specified as a file reference, only have an absolute reference – and in that case, the way the file is referenced depends on the OS. We currently access our ECV via http:// – this has all sorts of drawbacks (though I do see the uses for having it work over http://). I attempted setting things up so that use a file reference, but it turned out to be very “unportable” if the computer opening the EAF could not resolve the location, e.g. opening a EAF last saved by a Mac with a mounted network device, on a Windows machine accessing the same folder but through a Windows SMB network share.

I may not have throught this through properly but if ECV file references could be a bit more flexible in this regard, it would mean our ECV could live in a parallel directory to the EAFs and not have to be stored on a web server somewhere.

January 18, 2019 at 16:28 #12610

Han

Hi Matt,
I’ll add it to the wishlist.
The url of an ECV is, as you’ve seen, stored in an external reference element which is also used for other purposes; this might complicate things a bit (more).
I don’t know this part of the code that well, but the convenient side of the current situation is that loading of the ECV can be done more or less separately, without having to know the location of the document it is loaded for. But in principle it is all doable, I guess.

If I remember well, a long time ago, for audio and video files it was such that the way their location is stored in eaf, allowed them to be found cross-platform, even if they were stored on a local (SMB) network share, provided the location wasn’t stored based on their mount point but as the //server/share/folder/file address. I’m not sure if that (still) works, you probably already tried that.

-Han

January 21, 2019 at 12:45 #12614

Matt Brown

Thanks Han –

>> provided the location wasn’t stored based on their mount point but as the //server/share/folder/file address. I’m not sure if that (still) works, you probably already tried that.

Actually I’m not sure that I did. We have things set up a bit differently (and better) now and it’s working out well – but the next time we review our ECVs, I’ll test this out properly.

Cheers

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.