You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At trainings, a photographer takes a picture of each trainee. These are uploaded to the system and shown on their personnel pages. They are also used in the laminate printing process in a separate system. Photos are generally cropped before upload so that they're a useful headshot for a laminate.
It looks like paperclip plus paperclip-meta plus paperclip_database may make this fairly easy.
A Person has_one laminate_photo
Prevent DoS attacks by setting a reasonable file size default, large enough for 12 megapixels perhaps
Photos should be thumbnailed to a common size for display (100? 128? 150?)
Photos should be displayed on Person and Involvement pages
People with the Photographer or Laminates role can create a Photograph
Consider a bulk photo adding view with an upload button for each person at a training
Flexibility in photo storage implementations (set in config/environments) might be nice if it's easier to use the filesystem than a database in development. It would be nice if the production version stored photos in the database so a single export is needed to move from the 'net to the Playa or a test instance.
The text was updated successfully, but these errors were encountered:
At trainings, a photographer takes a picture of each trainee. These are uploaded to the system and shown on their personnel pages. They are also used in the laminate printing process in a separate system. Photos are generally cropped before upload so that they're a useful headshot for a laminate.
It looks like paperclip plus paperclip-meta plus paperclip_database may make this fairly easy.
The text was updated successfully, but these errors were encountered: