I’ve used Tainacan successfully for over a year with Safari web browser. Unfortunately, after this new 1.0.0 update, when viewing a collection I have made, and viewing it in “Table” view, I no longer can view the uppermost part of that window. (See my attached photo). In that photo, you will see that I scrolled to the very top of the page and anything currently hiding under the banner containing the words "Items from Collection CAPF COLLECTION” is not visible, nor can I access it. As you can see in my picture, the top portion of the letters of the teal coloured words “Collapse all” are even cut off. Not being able to see what’s under that banner, means not only do I not have access to "Advance search field”, but I’m also missing a number of other functions I need, like all the choices in the now hidden row such as the dropdown menus for “Metadata”, “Sorting”, “Visualization”, and “View as…”.
Also, I have 5 separate collections in the Repository. With your recent update, where can I now find the Repository-wide “Search” field that will simultaneously search all of my collections at the same time, like I used to be able to do before this update? It used to reside in the upper portion of the screen on the "Collections” page.
I don’t want to be forced to install Chrome or Firefox. Tainacan worked perfectly with Safari before your update.
In “Table” view, can you please add the functionality of freezing the 3 rows indicated in my 2nd attached photo. The columns header row names, should always be visible when I scroll down the 96 items per page in Table view. This is especially useful when a collection such as ours has many many columns of data. Can you please do this, while retaining the current functionality of being able to slide the elevator bars horizontally to move a large table horizontally?
We’re very sorry to hear that you are facing these issues. For starters, if these things are blocking your work, you can safely install the previous version while we work on this, although I will always recommend to keep in the latest version. Here is the zip. Just remember, if you go that way you might need to clear your browser cache reloading the admin page via CMD+SHIFT+R.
So let’s talk about the issues:
That is obviously not intencional and might be a bug. I don’t have a Mac to test on Safari but I’ll see if I can get in contact with some friends to debug and replicate that. The idea is that the top title header is fixed on scroll, but at start it should not collapse any of the content bellow and even if scrolled you should be able to return to the top.
Can you confirm to me if it really works if you change to Chrome or Firefox? I’m not expecting you to use them forever but it is good to be sure it is a browser or system-related issue. Also please provide me the version number of your Safari.
That is a UI change, a polemic one I might say, that we’ve made in this redesign. It has been tested by the community in our earlier mockups. The reasoning behind it is that the Header Search Bar gives a certain idea that there you have a “global” search, which could search in every content of your digital archive, when in reality:
It did not search in collections or taxonomies, only items, but even there it won’t look every metadata;
It sends the user to a repository-level list, where the available metadata and filters are only the repository-level ones or the core ones, and this caused certain confusion among users with less experience, especially those that have fewer collections and were not using repository-level features.
That does not mean in the future we don’t plan on having a sort of global search. I’m following really closely the development of the WordPress Command Palette component, which might be a good solution to offer quick navigation and search of content across the admin.
So for now, your alternative is to click on the “Items list” link in the “Collections” card:
That will take you to the Items list that you are familiar with and from there you can use the textual search input. A few extra clicks, I now, but it is a tradeoff that we’ve decided after careful consideration.
I actually gave this idea a try while I was implementing the Sticky page title headers. I can say that it is hard to implement because those three lines are inside different, nested wrappers and having the acknowledgement of who’s sticking so we can calculate the distance… it get’s messy . Besides that in smaller screens if we fix to many elements we end up loosing a lot of vertical space and it is hard to predict the variety of screen scenarios, view modes and even items per page number…
We do have some effort of overlapping elements in long lists that is a hidden but in my opinion insufficient solution. If you have your mouse hovering the items list and you’ve scrolled enough you may reach to the top or reach the bottom of the list to pull the Search Control and the Pagination inputs:
You’ll see that it is a bit clumsy. And again deciding which rows should be really freeze (title, search control, tabs, selection, table header) is a task that demands more user research in my opinion.
. Besides that in smaller screens if we fix to many elements we end up loosing a lot of vertical space and it is hard to predict the variety of screen scenarios, view modes and even items per page number…
