Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    lilimelgar
    @lilimelgar
    Yes, this, as mentioned above, required a lot of cleaning of the date fields. In some cases, e.g., in the Desmet film collection, when there is an uncertain creation date, for example, the cataloguer wrote: between 1910 and 1915, it is difficult to choose a single date. We created some rules to choose a single date in these cases, in order to facilitate the creation of the Media Suite time lines and for other ordering options. But this may create confusion for film historians, so, we are creating tooltips and adding documentation to clarify when these modifications took place.
    It would also be good to Help user go back to their results page while analysing results intermittently without having to use the browser 'Back' button.
    This is working as suggested now, and you will be able to test it in the forthcoming version :) @edekeulenaar
    It would be good to see why an item has been found, for example a Tour de France radio fragment was found for the search 'duurzaamheid AND luchthaven', because these terms occurred in the news excerpt in the transcript. Could e.g. indicate in which metadata field a match was found, or give some text fragments where the term was found.
    The new version will include highlighting terms from the query in the list of search results, so you can see where the term occurs. We will also check whether the new resource viewer (planned for next year) can include the term highlights for the individual result @TimelessFuture_twitter
    The workspace is not yet documented in Documentation, is this coming soon?
    Yes, this documentation has been slowly added in the past months, and will include more details in the forthcoming version
    I can't see in the list of search results which ones I have bookmarked, this would be useful for keeping track of what I have already done
    lilimelgar
    @lilimelgar
    @mwigham Thanks for this suggestion, this has been implemented and tested, and users will be able to use it in the forthcoming version :)
    Not quite appropriate to this room, but as I can't seem to find a better place... If I create a project and check the 'private ' box, then it doesn't seem to be visible anywhere
    A Workspace room is added, but no problem for using this room. The "Private" option doesn't work yet. All issues related to Collaboration are included in the roadmap for CLARIAH Plus.
    In the test version, when searching the radio collection, the results are not displayed correctly. In the regular version this is not a problem.
    This is fixed and tested, in the new production version (to be launched soon) this should be fine.
    lilimelgar
    @lilimelgar
    When switching back from viewing individual items to the result list, the list returns to the default setting of ordering by relevance. I'm currently using mostly the temporal ordering, with earliest items first. This means that each time, I have to reset the ordering to oldest first. It would be very nice if the setting last used would be saved, rather than returning to default (by relevance). Or, if that is too complex, to use the temporal ordering as the default, so that I only have to click that once to change to oldest first.
    The implemented Saved Queries allow to store the search parameters. This facilitates what you are suggesting. @jjnoordegraaf You will be able to test this further in the forthcoming version.
    Today we worked with the facets for filtering the KB newspaper collection on NRC Handelsblad and Telegraaf. Problem is that once you select a facet, the box closes immediately after; it is then not possible to reopen this unless you deselect the facet. It then becomes extremely hard to select more than one item from the facet list.
    As mentioned in relation to another suggestion above, there is a new feature in the Facet selector that allows you to select multiple facets, and also to have a "negative facet" selector. This will be available in the forthcoming version, where you could please test it :) @jjnoordegraaf
    lilimelgar
    @lilimelgar
    From project 8 presentation: would be good to be able to link people in metadata to people listed in other sources e.g. WikiData (NB: need to be wary of the 'filter' effects of the external source. For example, if it should turn out to be the case that there are more white males listed in WikiData than other groups, then those groups will automatically be underrepresented in links from the metadata, as they are less likely to be found on WikiData.
    Yes! that's one of the main aims for working with linked open data... Luckily, this work is progressing. This will be possible not for version 4 of the Media Suite, but in forthcoming versions in CLARIA Plus
    This message was deleted
    Search based on images
    @mwigham Apologies for late reply. You may have forgotten what this refer to, if not, could you please give more details about this request? thanks
    mwigham
    @mwigham
    This came from the Summer School, and I believe the request was to be able to upload an image and find similar images
    lilimelgar
    @lilimelgar
    Thank you Mari. @roelandordelman Is this included in the CLARIAH Plus roadmap?
    roelandordelman
    @roelandordelman
    Image-by-example could be a direction for image processing in plus.
    roelandordelman
    @roelandordelman
    @jblom Quote search doesn't seem to work properly. If I search for "Louise Kaiser" in NISV speech transcripts, I get results for "Merlijn Kaiser". Strangely, in previous versions it worked okay, but then used as a general/standard search. Currently, I don't find anything (zero results) via a standard query, I have to tick the asr box. Does that mean that general search is now limited to standard metadata or is this a bug? In any case, this should be: standard search uses all metadata (inclusive), the dropdown menu (or shortcut functions such as asr:test) allows you to search on specific metadata (exclusive).
    lilimelgar
    @lilimelgar
    Hi @roelandordelman Here some comments to your observations: (1) Roeland says: "Quote search doesn't seem to work properly. If I search for "Louise Kaiser" in NISV speech transcripts, I get results for "Merlijn Kaiser". Strangely, in previous versions it worked okay, but then used as a general/standard search". Our answer: Yes this is a bug when searching for exact phrases using quotation marks, it is reported here: beeldengeluid/labs-search-api#89 and it's in the backlog and @jblom knows about it
    @roelandordelman About the second topic, (2) the layers: this is not a bug ;) (please @jblom feel free to add/correct): Based on user input (see track here in Gitter, above, November 14,2018), we changed the labels of the layers to make more clear the distinction between "All metadata" (i.e., archival metadata), and "Enrhicments" (i.e., automatic enrichments for now, such as ASR or OCR). Now you see: All metadata and Enrichments as the top level categories with options within them. The two top level layers are mutually exclusive. In the Desmet paper collection, for example, OCR is in the enrichment layer, and has the same behavior.
    lilimelgar
    @lilimelgar
    @roelandordelman and @jblom: Since we have two separate indexes at the moment, and it's not possible to "search all metadata" including ASR, would it be better to use more consistent labels to make the two layers more clear? That is: instead of "Search in: all metadata fields" use "Search in: all Archive's metadata fields"? Screenshot
    roelandordelman
    @roelandordelman
    @lilimelgar and @jblom : before making fundamental changes, we have to define a clear strategy and design of the search interface. Let's take this up quickly as the current implementation is still a bit messy (or at least appears to be). In connection to this, every part (combinations) of the chosen search implementation has to be tested, maybe @mwigham can help here.
    roelandordelman
    @roelandordelman
    image.png
    @jblom @lilimelgar currently no video's are played in production
    (Chrome. cache deleted, Uni network, VPN/no-vPN)
    roelandordelman
    @roelandordelman
    same in Safari:
    image.png
    mwigham
    @mwigham
    @roelandordelman @lilimelgar @jblom Happy to help, this sort of testing has been mentioned a few times now, so it would be great if we can capture it in an issue (epic?), then we can schedule it in a sprint
    lilimelgar
    @lilimelgar
    @jblom @lilimelgar currently no video's are played in production @roelandordelman This is related to your cached, please do a hard refresh
    roelandordelman
    @roelandordelman
    nope, hard refresh does not help. You don't have issues @lilimelgar ?
    and now it works again... strange
    roelandordelman
    @roelandordelman
    @lilimelgar Found it! I have a privacy badger running that is causing the problem. Can you add this to the faq? (that privacy badgers may unexpectedly block playout).
    (this one should block "trackers" but does more)
    Jaap Blom
    @jblom
    ah that's a nice find @roelandordelman :-)
    On the topic of (ASR) search, we have mentioned this already several times. It's just a matter of prioritising so we can have this addressed properly (I'd say we need a white board session for this)
    lilimelgar
    @lilimelgar
    @lilimelgar Found it! I have a privacy badger running that is causing the problem. Can you add this to the faq? (that privacy badgers may unexpectedly block playout).
    @roelandordelman Sorry I didn't point you to the Troubleshooting section that was added to the documentation pages when we found this, I didn't understand your problem was with the playout.... http://mediasuite.clariah.nl/documentation/troubleshooting. Shall we add this section to the main menu to make it more visible?
    mwigham
    @mwigham
    Users find it irritating that the collection selection is reset every time they go to their workspace and come back
    mwigham
    @mwigham
    If the top result is annotated, then when you hover over the bookmark and the pop-up with the annotations appears, then it is partly obscured by the sort button
    roelandordelman
    @roelandordelman
    There is a bug when using "next resource" functionality: instead of the next resource the application consistently forgets the search results ONLY when the "relative" button is used in the plot. I tested with "Lubbers" (speech transcripts) without plot, with absolute plot and relative plot. Second video I get with relative plot is a "lingo" video.
    lilimelgar
    @lilimelgar
    Hi @roelandordelman Apologies for slow reaction, and thank you for reporting. I have been trying to reproduce the issue, but I don't find the bug that you found. I searched for "Lubbers" in the ASR, no date filters, clicked on the first result: "Casa Luna", and passed to the next results in the first page and until the second page. I did the same with date filters in the two cases (using absolute and switching to relative). I didn't encounter Lingo in any of these tests. If it's not too time consuming for you, could you please record a screencast? Otherwise, I can also look at this with you, please let me know via email or another channel when you are available.
    lilimelgar
    @lilimelgar

    If the top result is annotated, then when you hover over the bookmark and the pop-up with the annotations appears, then it is partly obscured by the sort button

    @mwigham Thank you Mari for reporting this. Because the Resource viewer is being redesigned at the moment, I will wait until the renovated version is ready for testing, to check if this issue occurs again. If it does, we will take action to fix it.

    lilimelgar
    @lilimelgar

    Users find it irritating that the collection selection is reset every time they go to their workspace and come back

    @mwigham Thank you again Mari for observing this. Since we will be working soon on planning small improvements to the collection selection workflow in the Media Suite, I am including this item in the issues to look at. You and other users will be notified here when this has been improved.