-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider saving content publication date in the ZIM #9
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
@Popolechien @rgaudin @mgautierfr @veloman-yunkan I would like to move forward with this. We need to have a way to store the original content date as ZIM Medatada. As a reminder, we already have the « Date » metadat which is automatically set and represents the ZIM creation date, see https://wiki.openzim.org/wiki/Metadata To me there is only questions about the naming:
IMO, we would benefit of using:
What do you think? |
Agrees with the proposal although I think explicit suffix would be better: I am not sure about the implications of renaming |
Why not
It would be nice to define all those therms now, even if we don't implement them. Appart that, I don't have a strong opinion on which term to use for what.
Creator should be updated but there will be no urgency on this as reader will have a lot of "old" zim file to handle anyway. |
"Date" is not optional says https://wiki.openzim.org/wiki/Metadata, @mgautierfr please open the necessary issues. I have no strong opinion on "Created" versus "Published". @rgaudin Any opinion? @mgautierfr Honestly, I believe to have defined "Published" and "Issued" clearly. What is unclear exactly? |
libzim never enforce the "Mandatory" property on metadata (except for Counter as it is created by libzim). The mandatory property is enforced at scrapper level (zimwriterfs does it, python-libzim and python-scrapperlib doesn't but maybe it is enforced in other tools). And I'm not sure we need to enforce it. What do we (libzim) do if user doesn't provide it ? We may refuse to create the zim file but we can detect this only at the end of the process, do we really want to wait the end of the creation to fail because On reader side, we don't expect
I agree with you definitions. My point is that there is another notion of date (when the zim itself is publish). This third notion cannot (and will not) be added to zim file but we should integrate this notion in our nomenclature as we may add it in the catalog (where it will have to be consistent with metadata pushed in zim file) |
I don't think we need an additonal one. "Published" is there and can be (and will be) superseeded in the CMS. Once the CMS takes the leadership on metadata, the time of the technical creation of the ZIM does not really matter anymore. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
And specify it is the ZIM specification.
For the moment, we have only the ZIM creation date, but this might be really different from the content publication date, in particular if the content is really old.
Folllowing a comment from https://github.com/veloman-yunkan at kiwix/libkiwix#702 (comment)
The text was updated successfully, but these errors were encountered: