Sure, understood. You can write scripts with simple guis, e.g. that's easy to do in Python in most OSes. Or you can put a web front-end on it. Or if you have a macro function in whatever system you use for storing your digital assets, that may work.
I bet if you find a local dev and say "make this easy to use for interns and part-timers" you can get a quote that's not crazy. On May 14, 2016 11:05:08 AM EDT, Joe Hoover work <joe.hoo...@mnhs.org> wrote: >That is why I emphasized "user-friendliness” unfortunately once you >get into doing scripting, no matter how simple, people have no >interest. I typically use scripting as well for running checksums but >this isn’t an option for others. I know there are several >checksum/hashsum apps out there and I was hoping to get some advice on >which folks are using and find useful. > > >> On May 14, 2016, at 8:43 AM, Matt Morgan <m...@concretecomputing.com> >wrote: >> >> This question gave me deja vu! Here's what I said 11 years ago in >reply to a related question: >> >> http://www.mail-archive.com/mcn-l@mcn.edu/msg08999.html >> >> I don't know if perl would be the right language, or is mdb is the >right way to keep the results, but this job is so easy to do with >simple scripts of almost any kind that I think I would still talk to a >developer and get a simple program/macro written, in whatever system(s) >you already use. >> >> Checksum utils tend to be cross-platform, and so are lots of >scripting languages, so I don't think you'd have significant >windows/mac issues going this route. >> >> Best, >> Matt >> >> On 05/13/2016 04:16 PM, Joseph Hoover wrote: >>> I am looking for recommendations for a user-friendly, affordable >Checksum >>> utility that is free-to-low-cost for small archives and history >>> organizations. Ideally, the utility would be able to batch process >digital >>> assets. Recommendations for checksum applications for both Mac and >Windows >>> would be very appreciated. >>> >>> Again "user-friendliness" is very important. Most the folks I help >are >>> usually volunteers that have no tech background. >>> >>> Thanks! >>> >>> _Joe >>> >>> >>> >>> _______________________________________________ >>> You are currently subscribed to mcn-l, the listserv of the Museum >Computer Network (http://www.mcn.edu) >>> >>> To post to this list, send messages to: mcn-l@mcn.edu >>> >>> To unsubscribe or change mcn-l delivery options visit: >>> http://mcn.edu/mailman/listinfo/mcn-l >>> >>> The MCN-L archives can be found at: >>> http://www.mail-archive.com/mcn-l@mcn.edu/ >> >> _______________________________________________ >> You are currently subscribed to mcn-l, the listserv of the Museum >Computer Network (http://www.mcn.edu) >> >> To post to this list, send messages to: mcn-l@mcn.edu >> >> To unsubscribe or change mcn-l delivery options visit: >> http://mcn.edu/mailman/listinfo/mcn-l >> >> The MCN-L archives can be found at: >> http://www.mail-archive.com/mcn-l@mcn.edu/ > >_______________________________________________ >You are currently subscribed to mcn-l, the listserv of the Museum >Computer Network (http://www.mcn.edu) > >To post to this list, send messages to: mcn-l@mcn.edu > >To unsubscribe or change mcn-l delivery options visit: >http://mcn.edu/mailman/listinfo/mcn-l > >The MCN-L archives can be found at: >http://www.mail-archive.com/mcn-l@mcn.edu/
_______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
