Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-25 Thread Nathan Tallman
I'm a little late to the thread, but I've used the self-hosted Chevereto for this sort of thing before. https://chevereto.com/ If you don't have a server, but some money, they offer hosting. Lychee also works well for this. https://lychee.electerious.com/ Nathan Nathan Tallman PGP Key

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-15 Thread Corey Halpin
GNU Mediagoblin might be worth a look if you're looking for something closer to Flickr than to a full DAMS: https://mediagoblin.org . Here's a couple of example MediaGoblin sites: https://papers.goblinrefuge.com https://media.libreplanet.org ~crh On 2017-11-13, Kari R Smith wrote: > Hi, > I

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-14 Thread Roy Tennant
Omeka could be overkill, depending on what your needs are. I have an Omeka site and frankly a lot of it is rather painful and counter-intuitive. If you're working with non-library folks, then the Dublin Core fields can be intimidating. If you don't need all that much, perhaps a hosted WordPress in

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-14 Thread Jessica Ann Sigman
I would also recommend Omeka. It's easy to manipulate and learn, and uses Dublin Core fields for metadata. On Nov 14, 2017 6:46 PM, "Kyle Banerjee" wrote: > I agree that it really depends on what is needed. For example, how many > images are there, what kind of capabilities do you need (e.g. m

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-14 Thread Kyle Banerjee
I agree that it really depends on what is needed. For example, how many images are there, what kind of capabilities do you need (e.g. metadata fields, searching, batch processing, workflows)? If your needs are simple enough, there's no particular reason why you couldn't just use the regular filesy

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-13 Thread Cary Gordon
That description takes in a lot of territory, so the answer, as usual, is “it depends”. Mostly, it depends on the nature of the metadata. If your objects are all TIFFs, you can place metadata in their files using EXIF and EXIF extensions. While elegant, it is not likely to be sufficient in most

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-13 Thread James, Eric
Using abode bridge to verify/add metadata to images: http://www.adobe.com/products/bridge.html I imagine you could use it with a shared folder of images or some workflow. Eric James Software Engineer Yale Center for British Art 1080 Chapel Street, PO Box 208280 New Haven, CT 06520-8280 203-432-

Re: [CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-13 Thread Laura Buchholz
Not sure about the sharing part, but Tropy (https://tropy.org/) from the CHNM might be worth a look. On Mon, Nov 13, 2017 at 6:27 AM, Kari R Smith wrote: > Hi, > I'm looking for solutions (can be open or paid for) for a group of people > to share, add to, and add metadata to digital images. Not

[CODE4LIB] Suggestion for an in-office sharable digital image asset system?

2017-11-13 Thread Kari R Smith
Hi, I'm looking for solutions (can be open or paid for) for a group of people to share, add to, and add metadata to digital images. Not Flikr ... but also not a full on asset management system, ideally. Thanks! -- Kari R.