Graphic Folders
Bruce Anschutz
Member Posts: 18 ✭✭
Comments
-
If security could be applied at the folder level, I'd be on board...Is that how you see this working? If not, I prefer the metadata option. It makes finding content easy. Just tag your content with descriptive tags like color, season, usage scenarios, etc... I've uploaded over 15,000 images, motion backgrounds, intro videos, and sermon support related items. I never have a problem finding things.0
-
I will attempt the metadata option. The only part of that I don't like is training new people on so many different aspects that they lose the ability to do the service with ease. As an example, each fall we launch a new 'theme' with a slew of different size and types of logos/background slides and it would be much easier in folders than teaching new people about metadata useage0
-
@Ryan Cowles Also not sure why you feel the need for 'security' at the folder level. If you have it all within the group upload folder anyway, why would security be such a concern? What am I missing here?0
-
@Bruce Anschutz
Security can be helpful if you wanted to disable the ability for a user to delete resources.... Like a read-only type of access at a folder level.0 -
@Bruce Anschutz
Have you tried using Boards in Proclaim? It's also metadata, but you can easily add and remove items to/from Boards in large groups of existing content. We use Boards with Metadata tags.
Since we have some screens that are 4:3 and others 16:9, I have a Board for each of those tags, then we have addition boards for Children's Church, Main Service, Back wall Screens, Pastoral Notes, and our Youth Group. Most everything uploaded gets added to more than one Board with at least five metadata tags to further describe the content and where it's appropriate to use.0 -
@Ryan Cowles I can understand that, but at the same time, if you're giving them access anyway they "should be" trustworthy enough. (Guess that's the 35 year Scouting veteran mentality showing through)0
-
@Bruce Anschutz
So far it's not a trust issue... It's happened accidentally.0
