[CODE4LIB] Baggit specification question

2014-08-06 Thread Rosalyn Metz
Hi all, Below is a question one of my colleagues posted to digital curation, but I'm also posting here (because the more info the merrier). Thanks! Rosy Hi, I am working for the Digital Preservation Network and our current specification requires that we use baggit bags

Re: [CODE4LIB] Baggit specification question

2014-08-06 Thread Tom Johnson
Also from 2.2.2: "All metadata elements are optional and MAY be repeated." Don't use Source-Organization: nil or Source-Organization: Simply omit any fields you don't wish to include in the bag. I believe the python and ruby libraries both handle this correctly. - Tom On Wed, Aug 6, 2014 at

Re: [CODE4LIB] Baggit specification question

2014-08-06 Thread Andrew Hankinson
I suspect the first example you give is correct. The newline character is the field delimiter. If you’re reading this into a structured representation (e.g., a Python dictionary) you could parse the presence of nothing between the colon and the newline as “None”, but in a text file there is no r