Mapping FileNet content files on the filesystem to their metadata in the database

Does anyone know how FileNet relates metadata from the Element table to the content files in the individual shelves?

There is what appears to be the unique identifier in the Element.ENAME field, but that doesn't match the syntax of the filenames on the file system. Those file names are similar to __2pq2aa_.001

There is an Ename_KW table that maps the ENAME to a KW field, but it's not known where that KW field is used.

Nowhere can we find out how the filename is mapped to the metadata. If anyone has any leads for us, they would be much appreciated.

Who is Participating?
Rsulliv1Connect With a Mentor Author Commented:
The filename is base 36 encoded. There doesn't appear to be any version information in the encoded filename although the file2id does output version information.

I'll close this thread, but I hope it helps someone else in the future!
Rsulliv1Author Commented:
it appears that there are some utility apps that can decipher the encoding, but I would still like to know the encoding algorithm, if possible.

The utilities were file2id and id2file.

Thanks again!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.