summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawk6I980MaZ8Xm0giW9VYpms1_vG13xurdw <Bob@web>2014-02-23 19:08:39 +0000
committerGravatar admin <admin@branchable.com>2014-02-23 19:08:39 +0000
commitdc08f90356ea9273a59d364352a8dfa500ba0445 (patch)
tree35bac14543fedc23bee62580daa3a375f501c2a0
parent733c6daeb4c432c8633a6c368ed5650e46690013 (diff)
-rw-r--r--doc/todo/Views_Demo.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/todo/Views_Demo.mdwn b/doc/todo/Views_Demo.mdwn
new file mode 100644
index 000000000..2587642e3
--- /dev/null
+++ b/doc/todo/Views_Demo.mdwn
@@ -0,0 +1,13 @@
+Joey,
+
+I've been thinking about leveraging git-annex for a workgroup document repository and I have just watched your views demo. The timing of the demo is great because I need to deploy a document repository with per-document metadata and your views concept seems like a great mechanism for associating metadata to documents and for displaying that metadata.
+
+While I don't expect to use your views concept for my workgroup repostory, a later iteration might do.
+
+The metadata in my use case begins with all the weird metadata seen on a book's copyright page. In addition, per-document provenance, like how one found the document and (if we're lucky) a URL where the latest version of the document may be found. Metadata values may be simple strings or may be markdown text.
+
+So, are you considering a metadata syntax that can support complex metadata? One example is multiple authors. Another issue is complex metadata values, like key=abstract and value="markdown text...".
+
+FWIW,
+
+Bob