[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] Re: Browse pages
Thanks all for the help on this. I think it?s started to get in there!
I?ve managed to make the changes I needed to the screen, but I?m still
struggling with the view. I get what needs to be done, however when I
change up the requisite view function in views.pl I get nothing.
For some reason the output of our creators is not in alphabetical order.
The function in views.pl is:
id => "creators",
allow_null => 0,
hideempty => 1,
menus => [
fields => [ "creators_browse_id" ],
new_column_at => [1, 1],
mode => "sections",
open_first_section => 1,
group_range_function => "EPrints::Update::Views::cluster_ranges_30",
grouping_function => "EPrints::Update::Views::group_by_a_to_z",
order => "-date/title",
variations => [
And you can see an output from that here:
I have looked here: http://wiki.eprints.org/w/Views.pl and implemented
some of the different parameters into the function, but the view does not
change. I?m restarting the server and setting ?Regenerate views? in admin
(all done on a local copy which is a replica of the live copy)
I?m wondering if I?m missing something?
On 10/06/2014 12:41, "Jan Ploski" <jpl at plosquare.com> wrote:
>The "browse by" pages are called "views".
>The module EPrints::Update::Views, traditionally invoked by the
>generate_views script and in newer versions of EPrints also triggered by
>requesting a stale view page, generates a separate HTML file for each
>view and for the summaries (how this occurs and which views are
>generated is driven by specifications in cfg.d/views.pl of your archive).
>In general, EPrints creates the XHTML document structure in memory first
>(by calling "appendChild" for each node) and in a final step it converts
>the content of this structure into a string, which is written either
>straight to browser or to a file.
>Strings that appear in the GUI are not found directly in the source
>code, instead they reside in phrases XML files. So typically you search
>the phrases files first to locate a piece of GUI (watching out for line
>breaks etc.), and in the next step you search for the phrase id in the
>source. However, with views it may not be the best approach because they
>mostly consist of data from the database, with few fixed phrases on
>which to base your search.
>You should just put some print STDERR "debug\n"; statements (goes to
>Apache rror log) or alter EPrint::Update::Views code and then observe
>what effect this has on the output of bin/generate_views.pl
>"Manage deposits" is quite a different story, it's a "screen"
>(implemented in EPrints::Plugin::Screen::EPrint::Deposit), as are most
>pages you see while navigating through EPrints. However, the output is
>done pretty much the same way, XHTML document structure constructed by
>the screen module, then output centrally. Note that the module
>Repository.pm (formerly Session.pm) contains quite a few functions that
>add more complex content to the XHTML document (they are called
>On 06/10/2014 11:50 AM, Andrew Beeken wrote:
>> Any thoughts? I find the method that EPrints uses to put pages together
>> rather impenetrable so any assistance would be great. I?m now also
>> at the Manage Deposits page and trying to make some adjustments to the
>> form there, however gripping for specific phrases from the form turns up
>> On 06/06/2014 14:42, "Andrew Beeken" <anbeeken at lincoln.ac.uk> wrote:
>>> I?m trying to understand how the ?Browse? pages are put together,
>>> specifically the ?Browse by creator? pages. I?ve tracked down the
>>> functions that seem to pull the content from the database but I?m not
>>> sure how this is then translated into a displayable page. Any pointers?
>>> The University of Lincoln, located in the heart of the city of Lincoln,
>>> has established an international reputation based on high student
>>> satisfaction, excellent graduate employment and world-class research.
>>> The information in this e-mail and any attachments may be confidential.
>>> If you have received this email in error please notify the sender
>>> immediately and remove it from your system. Do not disclose the
>>> to another person or take copies.
>>> Email is not secure and may contain viruses. The University of Lincoln
>>> makes every effort to ensure email is sent without viruses, but cannot
>>> guarantee this and recommends recipients take appropriate precautions.
>>> The University may monitor email traffic data and content in accordance
>>> with its policies and English law. Further information can be found at:
>>> *** Options:
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>> *** Options:
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
>*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>*** Archive: http://www.eprints.org/tech.php/
>*** EPrints community wiki: http://wiki.eprints.org/
>*** EPrints developers Forum: http://forum.eprints.org/