MetadataProvider and update

[Cantor, Scott]

> Out of curiosity: If he didn't want to stand up an MDQ server, couldn't he also
> just use the new dynamic provider file:// URL support in 2.6?  Maybe there's
> something about that I'm missing, I haven't actually used yet.

Probably, yes, that's an option. It's a bit messy because of the need to encode all the filenames.

> Where the $entityID substitution will be the SHA1 hash of the entityID.
> (Question: Is that the lower or upper case hex encoding of the hash? Or
> Base64, etc?  The docs don't really say).

Hex encoded (base64 doesn't make for good filenames), and I don't recall but I think it's lower case, and easy enough to try and see.

-- Scott