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

68 lines
1.5 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
-
update licenses from GPL to AGPL This does not change the overall license of the git-annex program, which was already AGPL due to a number of sources files being AGPL already. Legally speaking, I'm adding a new license under which these files are now available; I already released their current contents under the GPL license. Now they're dual licensed GPL and AGPL. However, I intend for all my future changes to these files to only be released under the AGPL license, and I won't be tracking the dual licensing status, so I'm simply changing the license statement to say it's AGPL. (In some cases, others wrote parts of the code of a file and released it under the GPL; but in all cases I have contributed a significant portion of the code in each file and it's that code that is getting the AGPL license; the GPL license of other contributors allows combining with AGPL code.)
2019-03-13 19:48:14 +00:00
- Licensed under the GNU AGPL version 3 or higher.
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
-}
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,
sqlite datbase for importfeed importfeed: Use caching database to avoid needing to list urls on every run, and avoid using too much memory. Benchmarking in my podcasts repo, importfeed got 1.42 seconds faster, and memory use dropped from 203000k to 59408k. Database.ImportFeed is Database.ContentIdentifier with the serial number filed off. There is a bit of code duplication I would like to avoid, particularly recordAnnexBranchTree, and getAnnexBranchTree. But these use the persistent sqlite tables, so despite the code being the same, they cannot be factored out. Since this database includes the contentidentifier metadata, it will be slightly redundant if a sqlite database is ever added for metadata. I did consider making such a generic database and using it for this. But, that would then need importfeed to update both the url database and the metadata database, which is twice as much work diffing the git-annex branch trees. Or would entagle updating two databases in a complex way. So instead it seems better to optimise the database that importfeed needs, and if the metadata database is used by another command, use a little more disk space and do a little bit of redundant work to update it. Sponsored-by: unqueued on Patreon
2023-10-23 20:12:26 +00:00
isLastChangedField,
itemIdField
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
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
fix build with old ghc
2019-01-18 18:09:35 +00:00
import Data.Monoid
import Prelude
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"
sqlite datbase for importfeed importfeed: Use caching database to avoid needing to list urls on every run, and avoid using too much memory. Benchmarking in my podcasts repo, importfeed got 1.42 seconds faster, and memory use dropped from 203000k to 59408k. Database.ImportFeed is Database.ContentIdentifier with the serial number filed off. There is a bit of code duplication I would like to avoid, particularly recordAnnexBranchTree, and getAnnexBranchTree. But these use the persistent sqlite tables, so despite the code being the same, they cannot be factored out. Since this database includes the contentidentifier metadata, it will be slightly redundant if a sqlite database is ever added for metadata. I did consider making such a generic database and using it for this. But, that would then need importfeed to update both the url database and the metadata database, which is twice as much work diffing the git-annex branch trees. Or would entagle updating two databases in a complex way. So instead it seems better to optimise the database that importfeed needs, and if the metadata database is used by another command, use a little more disk space and do a little bit of redundant work to update it. Sponsored-by: unqueued on Patreon
2023-10-23 20:12:26 +00:00
itemIdField :: MetaField
itemIdField = mkMetaFieldUnchecked "itemid"
Reference in a new issue Copy permalink