Hello, Another issue just reported for AGBU on the live (old) system. Normally when people checkout a cart, Alex (archivist) gets an automated message alerting him, so he can approve/reject.Today there was a cart request and he didn’t receive an automated message, so he had no idea. Can you look into why the automated notification was not sent? He received one yesterday at 12:42pm for a different request but did not get the one today, it is a critical piece of their workflow, Thanks
Hello Tracy, we had some maintenance tasks yesterday in the Email server, I think it was at the same time the cart was created, I just tested one simple email function in server now and email arrived ok. Can they test one Cart request to see if the email works now?
Hello Tracy, we had some maintenance tasks yesterday in the Email server, I think it was at the same time the cart was created, I just tested one simple email function in server now and email arrived ok. Can they test one Cart request to see if the email works now?
Dieneke, are we meeting today at 2pm eastern? I still seem to have old invites displaying on my calendar so i wanted to make sure that was accurate. Thanks.
Hello. A week or so ago, I mentioned that Alex wants to clean up folders on the beta that appear to be empty/testing, but he wants to confirm that these folders do not contain assets that he just can't see, or that they were not created by your team for testing purposes. Also, I want to confirm that Alex has access to see every asset. I didn't want to change his role to Admin, but as an Archivist, no asset should be hidden from him.
Hi Christopher. I found that on February 20, the date stamp of that m_2 hidden asset, was also the same date that you had to do an emergency restore of the site to the A location. You said that there was a hardware failure on the B site. So maybe something weird happened at that time. Also around that time, was when we had to relocate/reimport all of those missing assets, where we didn't have the original.
I just reviewed Archivist Vs Administrator permissions and the only difference is that Administrator can see hidden assets (there are around 2,000 deleted assets) that other roles like Archivist can't se, we can enable those assets too for the Archivist if you want.
Lightbox Functionality:
Users can filter, sort, and manually arrange files within the lightbox.
Files can be selected and ordered manually, allowing for greater control over the gallery's final display.
Sorting options will include default orders like date or name, with additional manual sorting for custom arrangements.
Thumbnail Sizing:
Use high-resolution images (800x800 or larger) for thumbnails in the gallery, allowing for dynamic resizing while maintaining quality.
URL Simplification:
The URLs for both galleries and carousels have been simplified, using a single prefix (/view/) and unique identifiers to differentiate between them, making the system more flexible for future updates.
Next Steps:
Sorting functionality is being finalized, and once completed, the system will support both default and manual sorting.
The deployment process for the new features was also discussed, with plans to implement changes by Friday, or whenever the remaining tasks are wrapped up
Gallery vs. Carousel Rendering Issues:
Problem: The gallery renders well but the carousel shows extra space on the top and bottom when embedded directly (no iframe).
Action: Fix this by setting a maximum height in the CSS for the carousel container.
Fixed Dimensions Problem:
Concern: Fixed dimensions for the carousel work on desktop but not on mobile, causing a non-responsive design.
Solution: Ensure the carousel remains responsive, avoiding fixed dimensions that break on mobile.
Iframe Use:
Previous Approach: Earlier versions used iframes for rendering, which worked without spacing issues.
Current Approach: No iframes are used, and the gallery renders well, but extra spacing issues arise with the carousel.
Mobile Responsiveness:
Problem: Fixed dimensions break mobile responsiveness.
Action: Explore a solution for maintaining responsive designs across all devices.
Caching and CDN Discussion:
CDN Usage: Currently, images are served directly from the server. No CDN is in use.
Recommendation: Consider implementing a CDN or a geolocated server setup to improve image load times, especially for international users.
Monitoring: Traffic and usage will be monitored over the next few months to decide on further CDN implementation.
Action Items: CSS Fixes for Carousel:
Action: Apply responsive CSS to prevent extra spacing on carousel. Add max height limits and test on different devices.
Thumbnail Rendition Fix:
Action: Fix thumbnail scaling issue to avoid blurriness, especially for the first impression.
Testing for Mobile:
Action: Test the carousel and gallery on mobile devices and desktops for responsiveness and any visual glitches.
Infrastructure Review:
Action: Monitor traffic and access logs to determine the need for CDN or server changes.
Tracy, AGBU Beta site got updated, scrolling issues got sovled, and I tried to replicate the search issue, they say, Searching for "vera setrakian" is not returning anything, but I did the search in bout (top Search Bar and Files> Summary Right Panel) and they both shows results. If they can try again or be little bit more explicit where exactly they are searching?
Thanks Cristobal. I gave this feedback to Alex, but they are focused on the big event this week so I probably will not hear back from him until next week. In the meantime, i have a user with the Subarchivist role that will be helping with creating galleries. Can you let me know what permissions i need to make sure are assigned for a role to have the correct gallery creation access?