scossu/pocket_archive
1
0
Fork 0
Code Issues 25 Pull requests Releases Packages Wiki Activity Actions

Separate date-time and timestamp data types #28

New issue
Open
opened 2026-01-26 14:18:01 +00:00 by scossu · 0 comments
scossu commented 2026-01-26 14:18:01 +00:00
Owner
Copy link

Currently, system-generated values for properties with a datetime type are entered as integer values (UNIX epoch, GMT). This is convenient for quick comparisons and can be easily converted to any date-time format.

However, this format is not convenient to use for user-provided data, and a different type should be used.

The datetime type should be used for user-provided dates and times and should be entered in the ISO8601 format, in UTC time zone: "%Y-%m-%dT%H:%M:%S"

The type for current system-generated numeric timestamps should be renamed timestamp.

Currently, system-generated values for properties with a `datetime` type are entered as integer values (UNIX epoch, GMT). This is convenient for quick comparisons and can be easily converted to any date-time format. However, this format is not convenient to use for user-provided data, and a different type should be used. The `datetime` type should be used for user-provided dates and times and should be entered in the ISO8601 format, in UTC time zone: `"%Y-%m-%dT%H:%M:%S"` The type for current system-generated numeric timestamps should be renamed `timestamp`.
scossu added this to the v1.0.0 milestone 2026-01-26 14:18:32 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
named_tree
v1.0b6
v1.0b5
v1.0b4
v1.0b3
v1.0b2
v1.0b1
v1.0a9
v1.0a8
v1.0a7
v1.0a6
v1.0a5
v1.0a4
v1.0a3
v1.0a2
v1.0a1
v1.0a0
Labels
Clear labels   
area/api

   
area/content_model

   
area/framework

   
area/io

   
area/presentation

   
area/preservation

   
area/rdf

   
area/security

   
area/submission

   
area/ui
  
p
critical
The issue is blocking major development tasks, is causing significant issues, or is a security/data integrity threat. It must be resolved before all other issues and must be in the current milestone.

  
p
high
The issue is causing notable problems. It must be in a milestone. It must be resolved in order for the milestone to be completed.

  
p
low
The issue may be in a milestone. It may be moved to another milestone or unassigned one, if necessary.

  
p
medium
The issue may be in a milestone. It should be completed in order to close the milestone.

  
s
blocked

  
s
done

  
s
progress

  
s
testing

  
s
wontfix

  
t
bug

  
t
documentation

  
t
enhancement

  
t
feature

  
t
test

No labels
area/api
area/content_model
area/framework
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
p
critical
p
high
p
low
p
medium
s
blocked
s
done
s
progress
s
testing
s
wontfix
t
bug
t
documentation
t
enhancement
t
feature
t
test
Milestone
Clear milestone
No items
No milestone
v1.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
scossu/pocket_archive#28
No description provided.