Dear Tibor, In data lunedì 21 gennaio 2008, Tibor Simko scribacchiaste dette parole: > Hi Sam: > $ bibdocadmin --record 8 --docname thesis --get-comment > This is foo and bar. > $ bibdocadmin --record 8 --docname thesis --set-comment "This is baz."
> Interesting missing actions: > > --stamp ... or maybe leave this for the above layer? > (--get-file && stamp.py && --revise-file ?) Talking with Nick, the stamping feature needs a template name and a dictionary-like set of key-values. In case we add this feature and maybe --create-icon too, we should find a nice way to provide all these data. > (BTW, there is a use case from Theodoros for a submitted file to > be viewable only after a certain date in the future, due to > copyright restrictions. We do not treat this in bibdoc so far. > We could eventually introduce the notion of "starting date" into > there.) What if we extends this to the whole authorization system by providing starting and ending value in general? Then creating a role 'anybody' we can authorize this role for a temporary access (or from now onwards). > BTW, if by the phrase "one or more result <action>" you mean we should > allow action chaining, then it could be misleading if people write > things like: > > --list-docnames --delete > What I meant was that if the query returns one and only record than lots of action where enabled. To enable all the actions regardless of how many records are we dealing with doesn't work because when you're revising a particular document or adding/appending a file you need to deal with a particular record at a time. I agree with you instead that action chaining is not a feature for such a tool. > > To let revise/add/append more than one data at a time we can think > > of having special symbols to divide them: say a '-' and '--' with > > the semantic: > > Again, it could be somewhat error prone if we allow treating of more > than one data object at the same time with different arguments. Maybe > people could do this only with bibupload FFTs. It is hard to combine > all the multi-multi options into a clean CLI interface. So I'd rather > prefer the CLI interface to be very simple and rock-solid, and for > complexish things, people could use MARCXML with FFTs, or the future > XML-based "inveniocfg" dump-edit-load tool. I was thinking of making the core of bibdocadmin based on FFT and bibdoc, hence to exploit all the possibilities offered by FFT. One of them is to add several format at a time. Unfortunatly at the moment this can't be done in otherway than by building a single FFT with all the formats in one go. Infact now that I'm thinking more about it, we can exploit the append action in order to provide a format at a time to a given document. So: bibdocadmin --record 123456 --docname foo (or --docid 654321) --append http://cern.ch/foo.ppt --format 'ppt' --comment 'blabla' bibdocadmin --record 123456 --docname foo (or --docid 654321) --append http://cern.ch/foo.tex --format 'tex' --comment 'blabla' bibdocadmin --record 123456 --docname foo (or --docid 654321) --revise-comment 'blabli' --format 'ppt' (what about hence for --revise-(comment|description|restriction|icon) and a separate --revise|--append for providing a url/filename, with optional --docname, --format, --comment, --description, --restriction, --icon, --doctype ? All the other not mentioned suggestions by you were accepted :-) Best regards, Sam -- .O. ..O OOO
