Closed jamiegau closed 4 years ago
Oh, while I remember, is there any specific naming convention against the DCP AnnotationText
? In my experience, it's commonly got the CPL ContentTitleText
in it, but when more then one CPL is in the DCP, that makes no sense. Is this field actually being used in the real world in anyway?
I have seen it commonly set to Empty
.
Yes. AnnotationText
is used prominently in the ingest manager of Doremi-derived GUI:s (DCP2000, IMSx000, ...). Each package is shown in a tree-like stucture in the GUI. If I remember correctly, for each package the AnnotationText
(from the PKL?) is used as the root node with each corresponding CPL ContentTitleText
as leaf nodes.
Thanks for the report, I added a prefix with the CPL names in those messages.
See #153
Seeings as your kicking around in that code.
Another small extra I would like is for ..
def console_progress_bar(file_path, progress, elapsed, done)
be enhanced to have
def console_progress_bar(file_path, progress_dcp, dcp_size, progress_file, file_size, elapsed, done)
So you can display overall progress, file progress and ETA for completion based on how long its been taking to process data up until that time.
Closing this issue as this is already discussed in #151
I find it strange that the results of the CHECK function do not indicate the target CPL the issues is connected to.
For example:
This is an example of a Flat/Scope bundled Trailer DCP. In this case, it found common issues with the DCNC in both CPLs, but there is no indication to which CPL they refer..
Even when utilising python code itself.. the
report
object returned has a list that contains theWARNING
list, however, no indication of CPL ContentTitleText or uuid is in the data returned.I cannot be the first to notice this??