mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-05-09 13:38:45 -04:00
parent 4025a92527
commit 6ad0b00849
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/todo/Bidirectional_metadata/comment_2_c791aca6da2bb1be70991bc1a76982a4._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2017-05-09T17:27:35Z"
content="""
I think that the core primitive here may not be the bidirectional
relationship, but instead setting a metadata field to a key.
If the metadata is known to be a key rather than some other type
of value, then key-specific things can be done with it.
So perhaps the real core thing is to be able to define what the type of a
metadata field is. That could be done using $field-type to define the type
of $field, but it seems it would be better to define it somewhat
globally so that fields with the same name can't have different types.
(The datalad project does something similar for tarballs, using a custom
special remote that retrieves the tarball as an annexed object and then
explodes it to get the requested member object.)
"""]]