Quote:
Originally Posted by culytera
Back again with another question, is it possible to format the date depending on whether the date published and date updated are the same or not?
...
Then I was thinking of comparing each published/updated month/day/year to form the final date, but I don't know if replace_metadata can take the value from other variables. Don't know why I can't just be satisfied with my current layout but here we are lol
|
(date)_format only works on the three standard date entries:
dateCreated,
datePublished, and
dateUpdated. The include_in_X mechanism make a list of strings, so it's not practical to change that.
And each replace_metadata line only works on one value at a time without knowledge of any other entry.
But I think it's possible to do what you want by using the _LIST feature of replace_metadata, this seems to work for me:
Code:
datePublished_format:%%B %%d, %%Y
dateUpdated_format:%%B %%d, %%Y
add_to_extra_valid_entries:,dateRange
include_in_dateRange:datePublished,dateUpdated
keep_in_order_dateRange:true
add_to_replace_metadata:
# same year 1 2 3 4 5
dateRange_LIST=>([^\s]+)\s+(\d{1,2}),\s+(\d{4}), ([^\s]+)\s+(\d{1,2}),\s+\3=>\1 \2-\4 \5, \3
# same month 1 2 3 4
dateRange_LIST=>([^\s]+)\s+(\d{1,2})-\1\s+(\d{1,2}),\s+(\d{4})=>\1 \2-\3, \4
# don't need regexp for date day, handled by de-dup.
- Explicitly set date formats--some sites also include times, those will be lost unfortunately
- Make new entry dateRange
- Populate dateRange with datePublished, dateUpdated
- Keep dateRange in order (otherwise alphabetized, not date ordered)
- Replace on dateRange_LIST (the whole list) looking for the same year -- note \3 matching the second year
- Replace on dateRange_LIST (the whole list) looking for the same month ONLY on strings that already had the same year -- note \1 matching the second month and - instead of ,\s+ between them.
- datePublished == dateUpdated and stories without dateUpdated will show up in dateRange as just one date.