Details
-
Task
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
None
-
None
-
None
Description
We're currently generating a "resourceName" in the PDFParser for incremental updates. The following isn't well documented (I don't think?), but we try to reserve "resourceName" for embedded files to be the actual name that the container document has for that embedded file.
Now, we need some kind of name for the embedded resource path in RecursiveParserWrapper, so we generate something based on the resourceName or, if that doesn't exist, the the relationship id, and if that doesn't exist we create /embedded-NUM.
But that's a separate issue.
We should use another option so that RecursiveParserWrapper knows to name the path /version-number-0 or similar. We should not misuse "resourceName".
Attachments
Issue Links
- links to