70000

700 GB

2.1 TB

3.5 TB

350 GB

1.05 TB

1.75 TB

70 GB

210 GB

350 GB

7 GB

21 GB

35 GB

Do we need to store the original image?

Yes

Amelia Sutton : no need to store the original image, only store the scaled image.

What scaled resolutions do we need to store?

Amelia Sutton: TBD, 100x100 minimum

Does anyone use FOLIO from mobile browsers?

Do we maintain the picture after a user has expired? 

Yes

Amelia Sutton: Yes

Do we support profile picture detention?

Yes

Amelia Sutton: Yes

How thumbnails should be generated? Cropping or Resizing?

Steve Ellis : Better to have a cropping mechanism on UI.

Amelia Sutton : Resizing on the longer side with whitespace on the sides. Cropping might be a future feature

Priyanka Terala : Cropping might require communication with Stripes core team. 

Kalibek Turgumbayev : Let's estimate the cropping approach.

Amelia Sutton : The SIG requests that images be scaled (without distortion) to fit within the space allotted in the relevant area of the UI. This would mean that there might be whitespace surrounding images that have a significant difference between their height and width, but will allow institutions to upload the images that they use in other systems without concern for adjusting for size. In the documentation for the profile pictures feature we will include recommended limits to aspect ratio that would not be enforced by the system. Even with this scaling it would be useful to allow images to be cropped using a cropping modal. So if you are able to find a React library that would allow for that to be implemented easily, it should be included in this initial feature.

File size limitations?

Yes

Kalibek Turgumbayev : The recommended limitation is 10MB

Amelia Sutton : UM SIG agrees to a 10MB limit

Should external links be stored in FOLIO?

Amelia Sutton : No. One of the institutions has a requirement not to store pictures on FOLIO side. Detailed requirements should be investigated

Steve Ellis : Cropping will not be possible.

Amelia Sutton: As per Thomas Trutt at Cornell (the primary institution that requires external storage for profile pictures), for their externally hosted images they will be using SSL with a static token supplied in the url so we do not need any considerations for authentication by FOLIO for externally hosted images. 

Should FOLIO support any export of data related to profile pictures?

Amelia Sutton : LOC and others will need functionality to migrate existing profile pictures from a previous system into FOLIO but this should be a separate feature. At the moment there is no requirement to allow export of profile picture data from FOLIO.

Do we need to support profile picture enabling on the fly? If yes, then it would be more complex than a single checkbox, because it will require providing storage type configuration

Amelia Sutton : No, it is acceptable to have the settings to enable and disable profile pictures on the back-end without any UI components.

Hi Amelia Sutton , 
In the Story UXPROD-36 its mentioned that - "Minimum accepted uploaded file type requirements: .heic .jpg .jpeg .png"

Question - Do we want to support .heic file type because HEIC is Apple's own format to store high resolution images made with iOS cameras. But I would store on backend JPG, because HEIC is not displayed in most browsers, not even in Safari. This will become an overhead in the implementation work. My suggestion is that lets take the minimalistic route (MVP) to accept images which are .jpg .jpeg .png type for the profile picture story. Your suggestions please.

CC: Adesh Singh , Irina Pokhylets , Kalibek Turgumbayev and Steve Ellis 

Amelia Sutton : Yes, .heic handling can be moved to a future enhancement.