aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment')
-rw-r--r--doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment16
1 files changed, 0 insertions, 16 deletions
diff --git a/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment b/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment
deleted file mode 100644
index 54cbe6fa6..000000000
--- a/doc/todo/metadata_--batch/comment_1_5cfe3b1a2847cfddd46ab6be249a74e4._comment
+++ /dev/null
@@ -1,16 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 1"""
- date="2016-02-19T19:18:41Z"
- content="""
-The metadata command is pretty complex. A batch interface would need to
-cover both setting and getting.
-
-There are four different ways to change a value, so it would probably
-make sense for the input to be of the form "file field=value"
-or "file field+=value" or "file field-=value" or "file field?=value"
-
-A field can have multiple values, including "". So, a batch interface
-to querying the value would need to handle that in its output. Perhaps
-json output?
-"""]]