...
- GOOD - "Just viewing" Methods: A) Create an account on your regular PF site with a general email and upload the scans to albums on that, then share the album (go to Collection Settings > Privacy). or B) Use a PF Proofing site and upload into "Events" via myLab.
- Pro: No account lookup needed. If you needed to protect the images from download, you could turn on the watermark which would turn off the download button. Or, if you
- Either: If wanted them to be able to download, they could on a regular PF site by not watermarking. Users cannot currently download images from a Proofing site (although that feature will be coming soon).
- Con: The album isn’t in an account and they always need the link to access it . so re-ordering or integrating with their other photos is not straightforward.
- BETTER - "Consumer owns the scans" Method: Even better – upload the scans right into the user’s account on your regular PF site. If they don’t have one, you create it for them. If they do have one, you can grab a temp password from myLab (go into the acct, click Generate One-Time Pass, that temp pass is good for a 1 hour window). Log in, then upload, just like consumers do. Tips: Standardize how you title the albums so they know what it is...their last name and the date...something to set it apart from personal uploads. They can always change it. Fill in the description too. Make sure to use Large upload so the biggest version is there for them to print with. You can even give them a special coupon code to encourage printing their new scans.
- Pro: The scans are part of the person’s account, and it’s easy for them to use to order from. And, anything to get members into your site is good. They can also download the images if they want.
- Con: You have collect the email beforehand (and ensure it's right), then look up (or create) the account. There is no way to prevent them from downloading the full res, since that watermark setting is one they would have access to turn on/off. You have to communicate with them by hand once it's done (there's not an email trigger for this).
...