LibraryOfCongress / bagit-spec

8 stars 7 forks source link

Consider adding Bag-Software-Agent to bag info well-known field list #33

Open acdha opened 6 years ago

acdha commented 6 years ago

According to https://github.com/search?q=bag-software-agent&type=Code there are Python, Ruby, Java, Scala, and Bash implementations of bagit which all set Bag-Software-Agent in bag-info.txt. Should we add that to the well-known field list in the spec?

cc: @dbrunton @johnscancella @justinlittman @jkunze

johnscancella commented 6 years ago

I think that is something we should add to the bagit.txt for bagit 2.0

justinlittman commented 6 years ago

Concur.

On Wed, Jun 13, 2018 at 6:46 AM John Scancella notifications@github.com wrote:

I think that is something we should add to the bagit.txt for bagit 2.0

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LibraryOfCongress/bagit-spec/issues/33#issuecomment-396895084, or mute the thread https://github.com/notifications/unsubscribe-auth/AAj6L5RfsSN8c3BnE2xqsRBn4BFEKovSks5t8O1mgaJpZM4UlJuF .

jkunze commented 6 years ago

+1

On Wed, Jun 13, 2018 at 3:47 AM, Justin Littman notifications@github.com wrote:

Concur.

On Wed, Jun 13, 2018 at 6:46 AM John Scancella notifications@github.com wrote:

I think that is something we should add to the bagit.txt for bagit 2.0

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LibraryOfCongress/bagit-spec/issues/33#issuecomment- 396895084, or mute the thread https://github.com/notifications/unsubscribe-auth/ AAj6L5RfsSN8c3BnE2xqsRBn4BFEKovSks5t8O1mgaJpZM4UlJuF .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LibraryOfCongress/bagit-spec/issues/33#issuecomment-396895363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAGaPA7QzYHgBUWPMD667ciQypwxZE5qks5t8O2qgaJpZM4UlJuF .

acdha commented 6 years ago

I was going to create a 2.0 (post 1.0?) milestone for this issue but that immediately raises the question of which repo is canonical. I'm wondering whether we should consider setting up a GitHub organization to hold bagit-related projects.