changing dates, daily notes (calendar) + timeline logics
complete
v
vision assemblies
often one ends up writing a note on a date that is not the relevant date in view of PKM / Journaling
– for these cases there should be a way to change / adapt 'creation dates'.
this is a problem known to anyone doing photo management, but also real journalling, or more to the point: people treating time as a relevant dimension in their PKM (see also 'Bringing the time dimension to the next level' @ https://capacities.io/roadmap/whats-next).
besides the practical question (need to adapt relevant date for structure / findability etc.), this question seems to interface w/ questions of general (future) Capacities-architecture at least at two levels:
1)
the calendar
is the only place which globally registers – in a very helpful way / structure / UI! – entries automatically on the basis of their date, their 'creation date' that is, up to now… a situation that also affords a lot of relevance / weight on the 'daily entries'
.– to really use / leverage this most helpful layer of Capacities one depends on creation date; – … which underlines why it would be so important to be able to modify this, or have any alternative kind of control over this structure (that is,
in the way the automatic + global registering based on timestamps
takes place)–… this also introduces some kind of ambivalency on the calendar already, as it mixes 'creation date' with 'journalling date'; a situation that gets even more tricky as soon as one also considers timeline-knowledge etc.
2) so, this also brings up again the
question of differences between database / file time, journalling and other – essential – time-based logics of PKM, like timelines
. (see also 👉 https://capacities.canny.io/feedback/p/timeline-view-for-databases-historical & https://discord.com/channels/940596022344843336/969304624848855050/1210505489423802418)– this kind of modification is exactly neccessary where users are forced to chose btw. database/file-time and other time-stamp logics relevant to journalling & knowledge management. so, e.g., currently the daily note carries all the weight, if one wants to have some kind of timeline representation (as there are no other ways for automated timelining)
so, this is both:
– a specific request 🙂
– a contribution (potentially) to the question of 'bringing the time dimension to the next level', and what that really could mean 😊
Log In
michael_v_h
complete
"Created at" dates can be modified now (will have to be added as a property first). For pages, go to table view, date can be changed in respective column. We will introduce time-based queries at some point to make it possible to query for specific dates/date ranges.
v
vision assemblies
michael_v_h All this is great!
(… maybe, keeping some kind of real timeline view on the radar / horizon list would nice too… – but it´s certainly an extra, given current dev map & tasks… )
M
Mike Oh
I’m very glad to be able to vote on and add to this enhancement request. As I see the immense potential for capacities in my life and work, I am starting to migrate content from other places as i use it.
I firmly agree with the pillar that all work is time-based, and am so thankful for the date note which includes all work on that date.
But i need to preserve the original create date of the content I’m importing. I need to be able to modify the create date of content so that it will appear on the correct day in my timeline, not the day I added it.
Thanks for your consideration!
Mike O.
michael_v_h
We recently made the created_at date editable. Does that work for you?
v
vision assemblies
hey michael_v_h ! thx for getting back directly!
yeah, I tried before posting, of course; but couldn't find a way.
just tried again. – maybe I am overlooking something obvious…?!
– is there any documentation for this? or do you have a hint where / how to achieve this? (which panel, command, etc.)?
thx a lot!
S
Stuart Gibbons
vision assemblies You need to add it as an object property
v
vision assemblies
Stuart Gibbons thanks a heap! 🙏
… I should have heeded my own regular advice 🤦… and read the documentation first.🙃 I kind of missed the obvious, as I just started getting myself into the logics of date / time here in practice…
I missed this link. and it´s intelligently implemented, in the usual Capacities way…🦉
what remains to me though, as questions (and still with a view to different time-relevancies / -logics) now (creation date; event date; journaling date:…):
• how do I search for dates?
• can I search for different
kinds
of dates, if 'kind' is not
congruent w/ object type?this still would seem to be a neccessity to systematically work with … say historical dates vs. file dates vs dates of registering… 🤔
are there any 'best practices' around this?
I think some kind of systematic overview into date / time w/ view of working with PKM / CAP and its different time-aspects (journal, timeline, etc.) would make sense to make all this more digestible for the 'everyone' people (like me in this case).
(regardless of this, I still can´t find a way to really modify the 'created at' date, as michael_v_h hinted as possible 🤔 – this would also come in handy in some contexts (retrospective entries, images etc. – so still interested in this too 👀)