Skip to content

CREATION_DATE not populated in report info #1532

Closed

Description

@karenhanson

I noticed while testing that Creation Date is no longer populated in the report. Is this a permanent change? When I looked at the code, I saw this is commented out with a note to fix it in the future, so it looks like there are plans to bring it back?:

// FIXME 2022 - report container info
// long l = container.getTimeEntry(OCFData.containerEntry);
// if (l > 0)
// {
// Date d = new Date(l);
// String formattedDate = new
// SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss'Z'").format(d);
// report.info(OCFData.containerEntry, FeatureEnum.CREATION_DATE,
// formattedDate);
// }

Activity

  1. rdeltour commented on Jul 7, 2023

    @rdeltour
    Member

    I saw this is commented out with a note to fix it in the future, so it looks like there are plans to bring it back?:

    Oh absolutely yes, thanks for the report. It looks like I missed this one when refactoring the container parsing code. I'm adding it to the next maintenance release.

  2. self-assigned this
    on Jul 7, 2023
  3. karenhanson commented on Nov 9, 2023

    @karenhanson
    Author

    @rdeltour Sorry to be a nuisance, but do you have a rough date for the next maintenance release? Just asking as I need to make a decision about whether to submit a PR to upgrade to EPUBCheck 5.1.0 in JHOVE or hold it back a bit longer. If it's likely to be more than a few months away I may do the PR now and add the CREATION_DATE field back in when it's available.

  4. rdeltour commented on Nov 17, 2023

    @rdeltour
    Member

    @karenhanson sorry for the late answer. The next maintenance release should be published at the end of this month!

  5. added
    status: in progressThe issue is being implemented by the development team
    and removed on Dec 23, 2024
  6. added a commit that references this issue on Dec 23, 2024
    d28e20f
  7. added
    status: has PRThe issue is being processed in a pull request
    and removed
    status: in progressThe issue is being implemented by the development team
    on Dec 23, 2024
  8. added a commit that references this issue on Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

status: has PRThe issue is being processed in a pull requesttype: regressionSomething that broke

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址