Difference between revisions of "Contribute: Plugins/ExportPluginsList"

From EPrints Documentation
Jump to: navigation, search
m (HelloList.pm)
(HelloList.pm)
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Export Plugin Tutorial 2: Hello, Lists =
+
[[Category:Contribute]]
 +
[[Category:Plugins]]
  
In this tutorial you will learn to create a slightly more complex export plugin than the one created in [[User:Tom/Export_Plugins/Hello_World| the previous tutorial]] that changes the way lists of eprints are exported.
+
= Export Plugin Tutorial 2: List Handling =
 +
 
 +
In this tutorial you will learn to create a slightly more complex export plugin than the one created in [[Contribute:_Plugins/ExportPluginsHello| the previous tutorial]] that changes the way lists of eprints are exported.
  
 
= HelloList.pm =
 
= HelloList.pm =
The code in the section below should be placed in a file called HelloList.pm in the directory created previously, and MyPlugins
+
The code in the section below should be placed in a file called HelloList.pm in the directory created previously.
should be changed to the name of that directory.
 
  
 
<pre>
 
<pre>
Line 40: Line 42:
 
         my ($plugin, %opts) = @_;
 
         my ($plugin, %opts) = @_;
  
         my $output = "ID\tTitle\n\n";
+
         my $r = [];
 +
 
 +
        my $header = "ID\tTitle\n\n";
 +
        if (defined $opts{fh})
 +
        {
 +
                print {$opts{fh}} $header;
 +
        }
 +
        else
 +
        {
 +
                push @{$r}, $header;
 +
        }
  
 
         foreach my $dataobj ($opts{list}->get_records)
 
         foreach my $dataobj ($opts{list}->get_records)
 
         {
 
         {
                 $output .= $plugin->output_dataobj($dataobj, %opts);
+
                 my $part = $plugin->output_dataobj($dataobj, %opts);
 +
                if (defined $opts{fh})
 +
                {
 +
                        print {$opts{fh}} $part;
 +
                }
 +
                else
 +
                {
 +
                        push @{$r}, $part;
 +
                }
 
         }
 
         }
  
         return $output;
+
        if (defined $opts{fh})
 +
        {
 +
                return undef;
 +
        }
 +
         return join('', @{$r});
 
}
 
}
  
Line 54: Line 78:
  
 
= In More Detail =
 
= In More Detail =
The above code is very similar to the HelloExport.pm file in [[User:Tom/Export_Plugins/Hello_World| the previous tutorial]] so only the points where it deviates significantly from that file will be discussed below.
+
The above code is very similar to the HelloExport.pm file in [[Contribute:_Plugins/ExportPluginsHello| the previous tutorial]] so only the points where it deviates significantly from that file will be discussed below.
  
 
== Housekeeping ==
 
== Housekeeping ==
Line 60: Line 84:
  
 
<pre>
 
<pre>
package EPrints::Plugin::Export::Foo::HelloList;
+
package EPrints::Plugin::Export::MyPlugins::HelloList;
 
</pre>
 
</pre>
  
Line 67: Line 91:
  
 
<pre>
 
<pre>
         $self->{name} = "Hello, List!";
+
         $self->{name} = 'Hello, List!';
 
</pre>
 
</pre>
  
Line 73: Line 97:
 
In this example the output_list method is overridden in the export plugin to provide column headers. The original method just concatenates the output from the output_dataobj subroutine called on every DataObj in the list.
 
In this example the output_list method is overridden in the export plugin to provide column headers. The original method just concatenates the output from the output_dataobj subroutine called on every DataObj in the list.
  
Note that the method is not provided with a bare array of DataObjs, but a List object is provided within the opts hash. To get an array of DataObjs to loop over you must then call that List object's get_record method.  
+
Note that the method is not provided with a bare array of DataObjs, but a List object is provided within the opts hash. To get an array of DataObjs to loop over you must then call that List object's get_record method.
 
 
If you try the plugin using the code below it will work from the web interface, however if you try to use the plugin through the command line export script you won't get any output. The solution is described in the next section.
 
 
 
<pre>
 
sub output_list
 
{
 
        my ($plugin, %opts) = @_;
 
 
 
        my $output = "";
 
 
 
        $output .= "ID\tTitle\n\n";
 
 
 
        foreach my $dataobj ($opts{"list"}->get_records)
 
        {
 
                $output .= $plugin->output_dataobj($dataobj, %opts);
 
        }
 
 
 
        return $output;
 
}
 
 
 
1;
 
</pre>
 
  
 
== Filehandles ==
 
== Filehandles ==
The command line export tool provides the output list method with a filehandle for output in the opts hash, while the cgi export uses a value returned from the method. You must deal with the filehandle or you will get no output from the command line tool. In most cases this won't matter, but it is good practice to deal with it.
+
The command line export tool provides the output list method with a filehandle for output in the opts hash, while the [http://en.wikipedia.org/wiki/Common_Gateway_Interface CGI] export uses a value returned from the method. You must deal with the filehandle or you will get no output from the command line tool. In most cases this won't matter, but it is good practice to deal with it.
  
 
The best way to handle output is to check if a filehandle has been provided every time something needs to be output. If a filehandle is provided we print to it, otherwise we save the output for later. At the end of the method we either return undef if a filehandle was provided or we return the saved output otherwise.
 
The best way to handle output is to check if a filehandle has been provided every time something needs to be output. If a filehandle is provided we print to it, otherwise we save the output for later. At the end of the method we either return undef if a filehandle was provided or we return the saved output otherwise.
 
Replace the code in output_list above with the code provided below.
 
  
 
<pre>
 
<pre>
Line 112: Line 112:
  
 
         my $header = "ID\tTitle\n\n";
 
         my $header = "ID\tTitle\n\n";
         if (defined $opts{"fh"})
+
         if (defined $opts{fh})
 
         {
 
         {
                 print {$opts{"fh"}} $header;
+
                 print {$opts{fh}} $header;
 
         }
 
         }
 
         else
 
         else
Line 121: Line 121:
 
         }
 
         }
  
         foreach my $dataobj ($opts{"list"}->get_records)
+
         foreach my $dataobj ($opts{list}->get_records)
 
         {
 
         {
 
                 my $part = $plugin->output_dataobj($dataobj, %opts);
 
                 my $part = $plugin->output_dataobj($dataobj, %opts);
                 if (defined $opts{"fh"})
+
                 if (defined $opts{fh})
 
                 {
 
                 {
                         print {$opts{"fh"}} $part;
+
                         print {$opts{fh}} $part;
 
                 }
 
                 }
 
                 else
 
                 else
Line 134: Line 134:
 
         }
 
         }
  
         if (defined $opts{"fh"})
+
         if (defined $opts{fh})
 
         {
 
         {
 
                 return undef;
 
                 return undef;
Line 144: Line 144:
 
= Testing Your Plugin =
 
= Testing Your Plugin =
  
Restart your webserver and test the plugin as in [[User:Tom/Export_Plugins/Hello_World| the previous tutorial]].
+
Restart your webserver and test the plugin as in [[Contribute:_Plugins/ExportPluginsHello| the previous tutorial]].
  
 
== Sample Output ==
 
== Sample Output ==
 
[[Image:Explist.png]]
 
[[Image:Explist.png]]

Latest revision as of 11:59, 12 February 2010


Export Plugin Tutorial 2: List Handling

In this tutorial you will learn to create a slightly more complex export plugin than the one created in the previous tutorial that changes the way lists of eprints are exported.

HelloList.pm

The code in the section below should be placed in a file called HelloList.pm in the directory created previously.

package EPrints::Plugin::Export::MyPlugins::HelloList;

@ISA = ('EPrints::Plugin::Export');

use strict;

sub new
{
        my ($class, %opts) = @_;

        my $self = $class->SUPER::new(%opts);

        $self->{name} = 'Hello, List!';
        $self->{accept} = [ 'dataobj/eprint', 'list/eprint' ];
        $self->{visible} = 'all';
        $self->{suffix} = '.txt';
        $self->{mimetype} = 'text/plain; charset=utf-8';

        return $self;
}

sub output_dataobj
{
        my ($plugin, $dataobj) = @_;

        return $dataobj->get_id()."\t".$dataobj->get_value('title')."\n";
}

sub output_list
{
        my ($plugin, %opts) = @_;

        my $r = [];

        my $header = "ID\tTitle\n\n";
        if (defined $opts{fh})
        {
                print {$opts{fh}} $header;
        }
        else
        {
                push @{$r}, $header;
        }

        foreach my $dataobj ($opts{list}->get_records)
        {
                my $part = $plugin->output_dataobj($dataobj, %opts);
                if (defined $opts{fh})
                {
                        print {$opts{fh}} $part;
                }
                else
                {
                        push @{$r}, $part;
                }
        }

        if (defined $opts{fh})
        {
                return undef;
        }
        return join('', @{$r});
}

1;

In More Detail

The above code is very similar to the HelloExport.pm file in the previous tutorial so only the points where it deviates significantly from that file will be discussed below.

Housekeeping

The package name has been changed to reflect the filename.

package EPrints::Plugin::Export::MyPlugins::HelloList;

Constructor

Make sure you give each plugin a unique name.

        $self->{name} = 'Hello, List!';

Dealing With Lists

In this example the output_list method is overridden in the export plugin to provide column headers. The original method just concatenates the output from the output_dataobj subroutine called on every DataObj in the list.

Note that the method is not provided with a bare array of DataObjs, but a List object is provided within the opts hash. To get an array of DataObjs to loop over you must then call that List object's get_record method.

Filehandles

The command line export tool provides the output list method with a filehandle for output in the opts hash, while the CGI export uses a value returned from the method. You must deal with the filehandle or you will get no output from the command line tool. In most cases this won't matter, but it is good practice to deal with it.

The best way to handle output is to check if a filehandle has been provided every time something needs to be output. If a filehandle is provided we print to it, otherwise we save the output for later. At the end of the method we either return undef if a filehandle was provided or we return the saved output otherwise.

sub output_list
{
        my ($plugin, %opts) = @_;

        my $r = [];

        my $header = "ID\tTitle\n\n";
        if (defined $opts{fh})
        {
                print {$opts{fh}} $header;
        }
        else
        {
                push @{$r}, $header;
        }

        foreach my $dataobj ($opts{list}->get_records)
        {
                my $part = $plugin->output_dataobj($dataobj, %opts);
                if (defined $opts{fh})
                {
                        print {$opts{fh}} $part;
                }
                else
                {
                        push @{$r}, $part;
                }
        }

        if (defined $opts{fh})
        {
                return undef;
        }
        return join('', @{$r});
}

Testing Your Plugin

Restart your webserver and test the plugin as in the previous tutorial.

Sample Output

Explist.png