not able to get the metadata values when passing the metadata for filename

asked on October 3, 2021

Hi,

We have an application that passes metadata to the LF server (on premise and cloud) for the filename of the document. These metadata are as follows:

The filename is submitted/passed using JRA's Document.create() method and as an example the format value is: %(Date).tif or %(Date/Time).tif.

However, when I check on the portal, the metadata value is not being pulled and instead, shows only the following:

I have tried creating/importing a document in portal (cloud and on-premise) and use the same format like below:

and it pulled the value successfully upon saving it (please see below screenshot)

My questions are:

1. Why is it not working when using the JRA in submitting the metadata?

2. Is there any workaround or any API we can use to fix this?

Please let me know. Thanks.

0 0

replied on October 4, 2021

Token resolution is outside the scope of what the SDK does - applications are responsible for resolving tokens and passing the desired name to the SDK. Technically, it would be challenging to do it otherwise, since an entry needs a name before it has any metadata associated with it. On the bright side, it means that you have full control over the format and range of the tokens your application supports.

0 0

replied on October 4, 2021

Thanks for your reply.

-> applications are responsible for resolving tokens and passing the desired name to the SDK

The question we have is about LF specific metadata. The application does not know the value it's associated with to resolve before passing it into the SDK. All the application knows is the metadata token name, i.e. %(Date). In fact, when this is passed in as value for a property field of a template from the application, it gets replaced with value properly after delivery. It only has issues when we try to use metadata as part of file name. However, if we enter the same file from the portal, i.e. %(Date).tif, it gets replaced with properly, as shown in the screen shot. What we see is inconsistency in two area:

1) Template property field (work) vs. File Name (not work)

2) Portal (work) vs. SDK (not work)

-> it means that you have full control over the format and range of the tokens your application supports.

The format and range of LF metadata tokens are controlled by LF, not the application. We can only control application specific token. The problem we have is LF metadata token.

0 0

Question

Question

not able to get the metadata values when passing the metadata for filename

Replies

Sign in to reply to this post.