mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
git-annex/Annex/MetaData/StandardFields.hs

62 lines
1.4 KiB
Haskell
Raw Normal View History

Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
{- git-annex metadata, standard fields
-
update my email address and homepage url
2015-01-21 16:50:09 +00:00
- Copyright 2014 Joey Hess <id@joeyh.name>
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
-
- Licensed under the GNU GPL version 3 or higher.
-}
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
{-# LANGUAGE OverloadedStrings #-}
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
module Annex.MetaData.StandardFields (
tagMetaField,
yearMetaField,
monthMetaField,
Add day to metadata when annex.genmetadata is enabled. Thanks, Sean T Parsons
2017-10-25 19:11:12 +00:00
dayMetaField,
don't copy old date metadata when adding new version of a file When adding a new version of a file, and annex.genmetadata is enabled, don't copy the data metadata from the old version of the file, instead use the mtime of the file. Rationalle being that the user has requested to generate metadata and so would expect to get the new mtime into metadata. Also, avoid warning about copying metadata when all the old metadata is date metadata. Which was rather the harder part. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
2018-04-04 17:42:15 +00:00
isDateMetaField,
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
lastChangedField,
toplevel lastchanged field
2014-03-19 23:10:35 +00:00
mkLastChangedField,
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
isLastChangedField
) where
import Types.MetaData
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
import qualified Data.Text as T
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
tagMetaField :: MetaField
tagMetaField = mkMetaFieldUnchecked "tag"
yearMetaField :: MetaField
yearMetaField = mkMetaFieldUnchecked "year"
monthMetaField :: MetaField
monthMetaField = mkMetaFieldUnchecked "month"
Add day to metadata when annex.genmetadata is enabled. Thanks, Sean T Parsons
2017-10-25 19:11:12 +00:00
dayMetaField :: MetaField
dayMetaField = mkMetaFieldUnchecked "day"
don't copy old date metadata when adding new version of a file When adding a new version of a file, and annex.genmetadata is enabled, don't copy the data metadata from the old version of the file, instead use the mtime of the file. Rationalle being that the user has requested to generate metadata and so would expect to get the new mtime into metadata. Also, avoid warning about copying metadata when all the old metadata is date metadata. Which was rather the harder part. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
2018-04-04 17:42:15 +00:00
isDateMetaField :: MetaField -> Bool
fix thinko for the second time It's almost like this part of haskell syntax is not very good..
2018-04-09 17:10:44 +00:00
isDateMetaField f
| f == yearMetaField = True
| f == monthMetaField = True
| f == dayMetaField = True
| otherwise = False
don't copy old date metadata when adding new version of a file When adding a new version of a file, and annex.genmetadata is enabled, don't copy the data metadata from the old version of the file, instead use the mtime of the file. Rationalle being that the user has requested to generate metadata and so would expect to get the new mtime into metadata. Also, avoid warning about copying metadata when all the old metadata is date metadata. Which was rather the harder part. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
2018-04-04 17:42:15 +00:00
toplevel lastchanged field
2014-03-19 23:10:35 +00:00
lastChangedField :: MetaField
lastChangedField = mkMetaFieldUnchecked lastchanged
mkLastChangedField :: MetaField -> MetaField
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
mkLastChangedField f = mkMetaFieldUnchecked (fromMetaField f <> lastchangedSuffix)
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
isLastChangedField :: MetaField -> Bool
toplevel lastchanged field
2014-03-19 23:10:35 +00:00
isLastChangedField f
| f == lastChangedField = True
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
| otherwise = lastchanged `T.isSuffixOf` s && s /= lastchangedSuffix
Each for each metadata field, there's now an automatically maintained "$field-lastchanged" that gives the timestamp of the last change to that field. Note that this is a nearly entirely free feature. The data was already stored in the metadata log in an easily accessible way, and already was parsed to a time when parsing the log. The generation of the metadata fields may even be done lazily, although probably not entirely (the map has to be evaulated to when queried).
2014-03-18 22:55:43 +00:00
where
s = fromMetaField f
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
lastchanged :: T.Text
toplevel lastchanged field
2014-03-19 23:10:35 +00:00
lastchanged = "lastchanged"
follow-on changes from MetaData type changes Including writing and parsing the metadata log files with bytestring-builder and attoparsec.
2019-01-07 19:51:05 +00:00
lastchangedSuffix :: T.Text
toplevel lastchanged field
2014-03-19 23:10:35 +00:00
lastchangedSuffix = "-lastchanged"
Reference in a new issue Copy permalink