EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08994
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Limit Export-search-results (max_items for export)
- To: <eprints-tech@ecs.soton.ac.uk>, "Stenger, Avischai" <avischai.stenger@tu-darmstadt.de>
 - Subject: Re: [EP-tech] Limit Export-search-results (max_items for export)
 - From: David R Newman <drn@ecs.soton.ac.uk>
 - Date: Tue, 5 Jul 2022 15:58:33 +0100
 
Hi Avischai,
Unfortunately, I don't think there is a way of
        limiting the number of records that can be exported.  I think
        the consideration at the time was that browse view web pages
        with loads of items can take a long time to load (even when
        cached) and they are not particularly useful to a user with
        their web browser as the page will be really long, (i.e. take
        forever to scroll through).  So rather than putting load on the
        server to generate such a web page it easier just to say, "this
        page has too many items to display".  The opposite is true with
        exports, which are typically machine-readable and therefore
        either used for some automated analysis or post-processed (e.g.
        truncated to only the first n items) before being displayed to a
        real user.  If an export itself was truncated or restricted if
        it had what was determined "too many items", this would then
        prevent or render the analysis/post-processing useless.  I am
        not sure what other people's thoughts are about this?
      
I think I may appreciate what might be your more general point, which is the high processing cost of generating these large exports. If you have some crawler going through your browse views and asking for every export format for some of these really long listings of items, it can put quite some load on the server, (/cgi/exportview is not cached). Sometimes, there can be multiple connections (maybe even 20+) from the same IP address trying to request view listing exports. I have observed crawlers doing this on a number of EPrints repositories and have had to resort to blocking the IP addresses, at least temporarily. We have been considering for future version of EPrints, if there is a way of restricting the number of requests that can make for processor-intensive pages over a set period of time:
https://github.com/eprints/eprints3.4/issues/102
Regards
David Newman
    
CAUTION: This e-mail originated outside the University of Southampton. Hi, I can limit the "max of founded Records" with „max_items“ in views.pl , but it looks like there is no limit for "export founded records“ So as I search after „roman“ and get the message "The number of items (7) for this view has exceeded system limits (6). The system administrator either needs to increase "max_items" or apply additional filters to this view.“ I can still klick on this Message-page on „export“ and get all the records. Is there a way to limit the permitted size (count) of records for the export? Regards & Tnks *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: https://eur03.safelinks.protection.outlook.com/?url=""> *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">
- References:
- [EP-tech] Limit Export-search-results (max_items for export)
- From: "Stenger, Avischai" <avischai.stenger@tu-darmstadt.de>
 
 
 - [EP-tech] Limit Export-search-results (max_items for export)
 
- Prev by Date: [EP-tech] Limit Export-search-results (max_items for export)
 - Next by Date: [EP-tech] Generate abstract by item type
 - Previous by thread: [EP-tech] EPrints/CRIS
 - Next by thread: [EP-tech] DOI handling in orcid_support_advance
 - Index(es):
 
