EPrints Documentation - User contributions [en-gb]

Main Page

2015-11-18T12:29:38Z

Lac:

[[Category:Rubbish]]
__NOTOC__
{{Box|title=EPrints Community Contributions Day|content=November 18th, 2015 is EPrints Community Contributions day. We encourage everyone to participate. See [[Community_Contributions_Day_November_2015|the event wiki page]]}}

'''Welcome to the EPrints Wiki'''

This wiki contains technical and user-contributed documentation for the [[Introduction|EPrints software]].

[http://demoprints3.eprints.org/ Demoprints] is our live, online server that allows anyone to try EPrints without having to install it first.

For more information on the EPrints project and related activities visit http://eprints.org/.

'''New to EPrints?'''

On this wiki you can find:

*Training videos (link to a page of these?)
*Documentation (link to)
*[[Working Groups]] by topic
*Mailing lists

There are two mail lists that you might like to join.

'''The EPrints User Group Google Group''' https://groups.google.com/forum/#!forum/eprints-uk-user-group

This group is for anyone involved in using EPrints. Ask questions, share ideas, hear about forthcoming meetings.

'''The Eprints Technical Mailing List'''

Join the list at: http://wiki.eprints.org/w/Contact

Offer solutions to peers or ask for help.

*How to contribute to the wiki (link to the contributing to the wiki section on main page)
*Code Sharing Repository https://github.com/eprintsug
*Help - The EPrints mailing lists are useful starting points

== Download EPrints ==

{{Download}}

==Installation==

* [[:Category:Installation|Installing]] EPrints on various platforms

==Getting Started==

* [[EPrints Manual|EPrints 3 Documentation]]
* [[Perl 101 for EPrints]]
* [http://www.eprints.org/software/training/ Training materials] provided by EPrints Services.
* [[Frequently Asked Questions]]
* [[:Category:Howto|How to...]]
* [[IRStats2 API]]
* [[EPrints_Training_Course|Training Videos]]

==Getting Support==

* [http://www.eprints.org/services/ EPrints Services] - premium support, training and hosting from EPrints experts
* [[Contact]] - mailing lists, bug reports etc.

==Add-ons, patches and translations==

* As of version 3.3 EPrints can now install plugins and translations through the [https://bazaar.eprints.org EPrints Bazaar] the wiki also has information about [[:Category:EPrints Bazaar|packaging plugins for the Bazaar]].
* The [http://files.eprints.org/ EPrints Files Repository] contains add-on and 3rd party scripts, patches and translations. This also provides an archive of all previous EPrints releases (3.0 onwards).
* [[:Category:Plugins|Plugins]]: Some Wiki pages about scripts and patches.

{{Register}}

==Contributing to EPrints==

* [[Usability|EPrints usability]]
* [[:Category:Releases|New features in EPrints]] - released and proposed
* [[How to contribute|How to contribute to EPrints development]]
* [http://trac.eprints.org/ EPrints Trac] - access nightly builds, tickets and changes (requires free registration to view source code)

== Content management ==

* [[Digital preservation]]: managing content for longer-term access and use

Main Page

2015-11-18T12:28:25Z

Lac:

[[Category:Rubbish]]
__NOTOC__
{{Box|title=EPrints Community Contributions Day|content=November 18th, 2015 is EPrints Community Contributions day. We encourage everyone to participate. See [[Community_Contributions_Day_November_2015|the event wiki page]]}}

'''Welcome to the EPrints Wiki'''

This wiki contains technical and user-contributed documentation for the [[Introduction|EPrints software]].

[http://demoprints3.eprints.org/ Demoprints] is our live, online server that allows anyone to try EPrints without having to install it first.

For more information on the EPrints project and related activities visit http://eprints.org/.

'''New to EPrints?'''

On this wiki you can find:

*Training videos (link to a page of these?)
*Documentation (link to)
*[[Working_Groups]] by topic
*Mailing lists

There are two mail lists that you might like to join.

'''The EPrints User Group Google Group''' https://groups.google.com/forum/#!forum/eprints-uk-user-group

This group is for anyone involved in using EPrints. Ask questions, share ideas, hear about forthcoming meetings.

'''The Eprints Technical Mailing List'''

Join the list at: http://wiki.eprints.org/w/Contact

Offer solutions to peers or ask for help.

*How to contribute to the wiki (link to the contributing to the wiki section on main page)
*Code Sharing Repository https://github.com/eprintsug
*Help - The EPrints mailing lists are useful starting points

== Download EPrints ==

{{Download}}

==Installation==

* [[:Category:Installation|Installing]] EPrints on various platforms

==Getting Started==

* [[EPrints Manual|EPrints 3 Documentation]]
* [[Perl 101 for EPrints]]
* [http://www.eprints.org/software/training/ Training materials] provided by EPrints Services.
* [[Frequently Asked Questions]]
* [[:Category:Howto|How to...]]
* [[IRStats2 API]]
* [[EPrints_Training_Course|Training Videos]]

==Getting Support==

* [http://www.eprints.org/services/ EPrints Services] - premium support, training and hosting from EPrints experts
* [[Contact]] - mailing lists, bug reports etc.

==Add-ons, patches and translations==

* As of version 3.3 EPrints can now install plugins and translations through the [https://bazaar.eprints.org EPrints Bazaar] the wiki also has information about [[:Category:EPrints Bazaar|packaging plugins for the Bazaar]].
* The [http://files.eprints.org/ EPrints Files Repository] contains add-on and 3rd party scripts, patches and translations. This also provides an archive of all previous EPrints releases (3.0 onwards).
* [[:Category:Plugins|Plugins]]: Some Wiki pages about scripts and patches.

{{Register}}

==Contributing to EPrints==

* [[Usability|EPrints usability]]
* [[:Category:Releases|New features in EPrints]] - released and proposed
* [[How to contribute|How to contribute to EPrints development]]
* [http://trac.eprints.org/ EPrints Trac] - access nightly builds, tickets and changes (requires free registration to view source code)

== Content management ==

* [[Digital preservation]]: managing content for longer-term access and use

Main Page

2015-11-18T12:27:47Z

Lac:

[[Category:Rubbish]]
__NOTOC__
{{Box|title=EPrints Community Contributions Day|content=November 18th, 2015 is EPrints Community Contributions day. We encourage everyone to participate. See [[Community_Contributions_Day_November_2015|the event wiki page]]}}

'''Welcome to the EPrints Wiki'''

This wiki contains technical and user-contributed documentation for the [[Introduction|EPrints software]].

[http://demoprints3.eprints.org/ Demoprints] is our live, online server that allows anyone to try EPrints without having to install it first.

For more information on the EPrints project and related activities visit http://eprints.org/.

'''New to EPrints?'''

On this wiki you can find:

*Training videos (link to a page of these?)
*Documentation (link to)
*[Working_Groups] by topic
*Mailing lists

There are two mail lists that you might like to join.

'''The EPrints User Group Google Group''' https://groups.google.com/forum/#!forum/eprints-uk-user-group

This group is for anyone involved in using EPrints. Ask questions, share ideas, hear about forthcoming meetings.

'''The Eprints Technical Mailing List'''

Join the list at: http://wiki.eprints.org/w/Contact

Offer solutions to peers or ask for help.

*How to contribute to the wiki (link to the contributing to the wiki section on main page)
*Code Sharing Repository https://github.com/eprintsug
*Help - The EPrints mailing lists are useful starting points

== Download EPrints ==

{{Download}}

==Installation==

* [[:Category:Installation|Installing]] EPrints on various platforms

==Getting Started==

* [[EPrints Manual|EPrints 3 Documentation]]
* [[Perl 101 for EPrints]]
* [http://www.eprints.org/software/training/ Training materials] provided by EPrints Services.
* [[Frequently Asked Questions]]
* [[:Category:Howto|How to...]]
* [[IRStats2 API]]
* [[EPrints_Training_Course|Training Videos]]

==Getting Support==

* [http://www.eprints.org/services/ EPrints Services] - premium support, training and hosting from EPrints experts
* [[Contact]] - mailing lists, bug reports etc.

==Add-ons, patches and translations==

* As of version 3.3 EPrints can now install plugins and translations through the [https://bazaar.eprints.org EPrints Bazaar] the wiki also has information about [[:Category:EPrints Bazaar|packaging plugins for the Bazaar]].
* The [http://files.eprints.org/ EPrints Files Repository] contains add-on and 3rd party scripts, patches and translations. This also provides an archive of all previous EPrints releases (3.0 onwards).
* [[:Category:Plugins|Plugins]]: Some Wiki pages about scripts and patches.

{{Register}}

==Contributing to EPrints==

* [[Usability|EPrints usability]]
* [[:Category:Releases|New features in EPrints]] - released and proposed
* [[How to contribute|How to contribute to EPrints development]]
* [http://trac.eprints.org/ EPrints Trac] - access nightly builds, tickets and changes (requires free registration to view source code)

== Content management ==

* [[Digital preservation]]: managing content for longer-term access and use

Working Groups

2015-11-18T12:27:04Z

Lac: Created page with '*Open Access *Research Data Management *Impact *Funding *Reporting *Standards - CASRAI'

*[[Open Access]]
*[[Research Data Management]]
*[[Impact]]
*[[Funding]]
*[[Reporting]]
*[[Standards]] - CASRAI

WorkingGroups

2015-11-18T12:26:33Z

Lac: Created page with '*Open Access *Research Data Management *Impact *Funding *Reporting *Standards - CASRAI'

*[[Open Access]]
*[[Research Data Management]]
*[[Impact]]
*[[Funding]]
*[[Reporting]]
*[[Standards]] - CASRAI

Standards

2015-11-18T12:25:44Z

Lac: Created page with '==Purpose== The Standards working group... ==Members=='

==Purpose==

The Standards working group...

==Members==

Reporting

2015-11-18T12:25:24Z

Lac: Created page with '==Purpose== The Reporting working group... ==Members=='

==Purpose==

The Reporting working group...

==Members==

Funding

2015-11-18T12:25:11Z

Lac: Created page with '==Purpose== The Funding working group... ==Members=='

==Purpose==

The Funding working group...

==Members==

Impact

2015-11-18T12:24:56Z

Lac: Created page with '==Purpose== The Impact working group... ==Members=='

==Purpose==

The Impact working group...

==Members==

Research Data Management

2015-11-18T12:24:42Z

Lac: Created page with '==Purpose== The RDM working group... ==Members=='

==Purpose==

The RDM working group...

==Members==

Category:WorkingGroups

2015-11-18T12:24:15Z

Lac:

*[[Open Access]]
*[[Research Data Management]]
*[[Impact]]
*[[Funding]]
*[[Reporting]]
*[[Standards]] - CASRAI

Category:WorkingGroups

2015-11-18T12:23:46Z

Lac:

*[[Open Access]]
*[[Research data management]]
*[[Impact]]
*[[Funding]]
*[[Reporting]]
*[[Standards]] - CASRAI

Open Access

2015-11-18T12:22:35Z

Lac:

==Purpose==

The Open Access working group...

==Members==

Open Access

2015-11-18T12:22:08Z

Lac: Created page with '==Open Access== The Open Access working group...'

==Open Access==

The Open Access working group...

Main Page

2015-11-18T12:15:51Z

Lac:

[[Category:Rubbish]]
__NOTOC__
{{Box|title=EPrints Community Contributions Day|content=November 18th, 2015 is EPrints Community Contributions day. We encourage everyone to participate. See [[Community_Contributions_Day_November_2015|the event wiki page]]}}

'''Welcome to the EPrints Wiki'''

This wiki contains technical and user-contributed documentation for the [[Introduction|EPrints software]].

[http://demoprints3.eprints.org/ Demoprints] is our live, online server that allows anyone to try EPrints without having to install it first.

For more information on the EPrints project and related activities visit http://eprints.org/.

'''New to EPrints?'''

On this wiki you can find:

*Training videos (link to a page of these?)
*Documentation (link to)
*[[:Category:WorkingGroups|Working Groups]] by topic (link to - see below)
*Mailing lists

There are two mail lists that you might like to join.

The EPrints User Group Google Group https://groups.google.com/forum/#!forum/eprints-uk-user-group

This group is for anyone involved in using EPrints. Ask questions, share ideas, hear about forthcoming meetings.

2) The Eprints Technical Mailing List
Join the list at: http://wiki.eprints.org/w/Contact

Offer solutions to peers or ask for help.

*How to contribute to the wiki (link to the contributing to the wiki section on main page)
*Code Sharing Repository https://github.com/eprintsug
*Help - The EPrints mailing lists are useful starting points (link to mail list bit)

== Download EPrints ==

{{Download}}

==Installation==

* [[:Category:Installation|Installing]] EPrints on various platforms

==Getting Started==

* [[EPrints Manual|EPrints 3 Documentation]]
* [[Perl 101 for EPrints]]
* [http://www.eprints.org/software/training/ Training materials] provided by EPrints Services.
* [[Frequently Asked Questions]]
* [[:Category:Howto|How to...]]
* [[IRStats2 API]]
* [[EPrints_Training_Course|Training Videos]]

==Getting Support==

* [http://www.eprints.org/services/ EPrints Services] - premium support, training and hosting from EPrints experts
* [[Contact]] - mailing lists, bug reports etc.

==Add-ons, patches and translations==

* As of version 3.3 EPrints can now install plugins and translations through the [https://bazaar.eprints.org EPrints Bazaar] the wiki also has information about [[:Category:EPrints Bazaar|packaging plugins for the Bazaar]].
* The [http://files.eprints.org/ EPrints Files Repository] contains add-on and 3rd party scripts, patches and translations. This also provides an archive of all previous EPrints releases (3.0 onwards).
* [[:Category:Plugins|Plugins]]: Some Wiki pages about scripts and patches.

{{Register}}

==Contributing to EPrints==

* [[Usability|EPrints usability]]
* [[:Category:Releases|New features in EPrints]] - released and proposed
* [[How to contribute|How to contribute to EPrints development]]
* [http://trac.eprints.org/ EPrints Trac] - access nightly builds, tickets and changes (requires free registration to view source code)

== Content management ==

* [[Digital preservation]]: managing content for longer-term access and use

Category:WorkingGroups

2015-11-18T12:09:30Z

Lac:

*[[Open Access]]
*Research data management
*Impact
*Funding
*Reporting
*Standards - CASRAI

Category:WorkingGroups

2015-11-18T12:07:10Z

Lac: Created page with '*Open Access *Research data management *Impact *Funding *Reporting *Standards - CASRAI'

*Open Access
*Research data management
*Impact
*Funding
*Reporting
*Standards - CASRAI

New Features in EPrints 3.2

2009-05-08T06:52:51Z

Lac: /* Linked Data Support */

= EPrints Edit locking =

Allows you to lock editing to certain users and sessions (to make sure that two editors don't make simultaneous changes to the same record).

Expected: Beta 1

= Plug-in Based Storage Layer and Storage Controller =

The EPrints Storage Layer is evolving to enable easy plug-and-plug with many storage platforms including local and multiple institutional storage as well as cloud storage. The Storage Controller enables you to use multiple storage platforms simultaneously, define rules for what is stored on each platform and also manage these platforms and migrate resources between platforms as required. More information, including the current API, can be found on the [[StorageController]] page.

Expected: Beta 1

= Thumbnails are now documents =

Up to now, thumbnails have been 'special case' files that have not been managed very consistently by the repository. In particular, there has been no way to create or manage thumbnails through the API. Now, thumbnails and document previews are normal documents of a specific type and specific relationships to other documents. This allows a much more flexible approach to be taken to thumbnails, with multiple size and multiple formats being produced by external services. It also becomes possible to have more complex categories of thumbnail, for example a different thumbnail for every slide in a PowerPoint slideshow, not just a thumbnail of the front slide. That in turn allows EPrints to potentially build visual catalogues of collections of PowerPoint presentations.

Expected: Beta 1

= SWORD 2 (1.3 Specification Support) =

Conforming to the new standards set out by the SWORD project, EPrints 3.2 will include compatibility for the new features.

Expected: Beta 1

= Preservation Planning Capabilities =

Allows EPrints to be linked with file classification tools (primarily DROID) and risk analysis services (PRONOM) which can then not only profile the content of your repository but also identify risks to objects contained within it.

More information on this can be found on the [[Preservation in EPrints 3.2]] page.

Expected: Beta 1

= Enhanced Compatability for DRIVER project systems =

In EPrints 3.2 repositories will be by default DREIVER enabled. In a future 3.1 release the better compatability will exist but will remain off by default.

Expected: EPrints 3.1 and 3.2.

= Arbitrary metadata linking capabilities =

Allows the user to expand their data model with custom predicates which link a resources with other resources. Such an example include the derivedFrom predicate which we are already using.

Expected: Beta 1

= docx,xslx,pptx MS Office XML compatability =

Upon upload of these file types EPrints 3.2 will automatically fill in much of the metadata such as title, authors and abstract if possible. 3.2 will also be able to pull these files apart offering optional access to the content within them such as embedded pictures.

Expected: Beta 1 (tentative)

= Enhancements to repository web site management =

Taking on the push of 3.1 to make it easy for the repository manager to edit and change the repository configuration without needing access to the configuration files themselves, we are taking that another step further. Coming in 3.2 we intend to allow full look and feel (branding) editing of the main EPrints web pages and templates to be done externally to EPrints in tools such Dreamweaver and Amaya. There will also be a complementary way of uploading new image files.

This editing capability is also complemented by two links which appear on certain pages enabling the administrator to directly edit the page look and feel as well as the phrases on that page.

Expected: Beta 1

= Abstract Page Improvements =

Lightboxes have been added to the abstract pages for easier previewing of documents.

Expected: Beta 1

= User definable datasets =

Allows you to expand the core EPrints data model with whole new types of data and datasets which can be indexed and used in searches. It is proposed that the stakeholders in the CERIF standard (projects, authors, institutions etc) will be modelled as separate EPrints datasets and used to support Research Management activities and integration with Research Information Systems.

Expected: Beta 1 (command line only)

= OAI-ORE Import and Export Plug-ins =

Capability to import and export resources or collections of resources as ORE Resource Maps. Both Atom and RDF serialisations are planned to be made available.

Expected: Beta 1

= IRStats/EPStats =

Institutional Repository stats are becoming an even more important part of the repository and we hope to have these in the final 3.2 release.

Expected: Beta 1

= EPrints Scheduler =

Allows tracking of events which happen as well as scheduling new events which need to take place to maintain your repository. Investigation is under way into the power of such a system and if it can be interfaced with desktop calendar programs such as iCal and Google Calendar.

Expected: Beta 2

= Shelves of EPrints =

No details to be released on this yet

Expected: Beta 2 (tentative)

= Coverpage capabilities =

Provides a mechanism for adding coverpages to documents before they are provided to users.

Expected: Beta 2 (tentative)

= Issues Raising and Resolving Tool =

No description currently

Expected: Beta 2 (tentative)

= Plugin system for document upload processing =

So zip,targz,file, from URL etc. become a plugin each and we add Docx/PPTx too.

Expected: Beta 1 (tentative)

= FTP and WebDAV Daemon Support =

Access to the user's inbox via FTP and WebDAV, allowing the repository to be mounted as a file system or network drive.

Expected: Beta 1 (tentative)

= Multi-stage editorial buffer =

If an institution has a number of stages to the editorial process (e.g and editor to check the metadata, followed by a different(?) editor to check copyright), they should be able to configure editor roles and buffer stages.

Expected: Beta 2 (tentative)

= User Profiles =

For those without institutional 'people' pages, EPrints will generate a page for each user containing information including a list of publications and perhaps a picture.

= Institutional GeoLoc Authority and Autocompletion =

Implementation of an optional institution autocompletion script (for e.g. conference repositories) that autocompletes on an authority file containing canonical institution names and coordinates.

= REST Interface =
Creating a proper REST interface for EPrints CRUD operations. E.g.
http://devel.eprints.org/eprint/103/creators/1/name/family.txt
will return a text form of the family component of the namer of the first creator of eprint id 103.

= Linked Data Support =
EPrints is now represented on the Linked Data map (see http://linkeddata.org/ ). It currently has an RDF exporter, but it lacks a systematic way of coining appropriate institutionally-blessed URIs for individuals, projects etc. A new version of the RDF plugin will be released which enables repositories to participate in the international linked data effort.

= ISI Citation Data Management =
As well as Google Scholar citation data, EPrints 3.2 adds the capability of managing Thomson ISI citation data. EPrints will harvest citation data, displaying it on abstract pages. Items can be searched by citation range, searches can be ordered by citation impact and aggregate reports of citation statistics (including h-index) can be produced per research group or subject area using the citation report export plugin.

New Features in EPrints 3.2

2009-04-17T14:05:28Z

Lac: /* Institutional GeoLoc Authority and Autocompletion */

New Features in EPrints 3.2

2009-02-25T20:32:40Z

Lac: /* Thumbnails are now documents */

= EPrints Edit locking =

Allows you to lock editing to certain users and sessions (to make sure that two editors don't make simultaneous changes to the same record).

Expected: Beta 1

= Plug-in Based Storage Layer and Storage Controller =

The EPrints Storage Layer is evolving to enable easy plug-and-plug with many storage platforms including local and multiple institutional storage as well as cloud storage. The Storage Controller enables you to use multiple storage platforms simultaneously, define rules for what is stored on each platform and also manage these platforms and migrate resources between platforms as required. More information, including the current API, can be found on the [[StorageController]] page.

Expected: Beta 1

= Thumbnails are now documents =

Up to now, thumbnails have been 'special case' files that have not been managed very consistently by the repository. In particular, there has been no way to create or manage thumbnails through the API. Now, thumbnails and document previews are normal documents of a specific type and specific relationships to other documents. This allows a much more flexible approach to be taken to thumbnails, with multiple size and multiple formats being produced by external services. It also becomes possible to have more complex categories of thumbnail, for example a different thumbnail for every slide in a PowerPoint slideshow, not just a thumbnail of the front slide. That in turn allows EPrints to potentially build visual catalogues of collections of PowerPoint presentations.

Expected: Beta 1

= SWORD 2 (1.3 Specification Support) =

Conforming to the new standards set out by the SWORD project, EPrints 3.2 will include compatibility for the new features.

Expected: Beta 1

= Preservation Planning Capabilities =

Allows EPrints to be linked with file classification tools (primarily DROID) and risk analysis services (PRONOM) which can then not only profile the content of your repository but also identify risks to objects contained within it.

More information on this can be found on the [[Preservation in EPrints 3.2]] page.

Expected: Beta 1

= Enhanced Compatability for DRIVER project systems =

In EPrints 3.2 repositories will be by default DREIVER enabled. In a future 3.1 release the better compatability will exist but will remain off by default.

Expected: EPrints 3.1 and 3.2.

= Arbitrary metadata linking capabilities =

Allows the user to expand their data model with custom predicates which link a resources with other resources. Such an example include the derivedFrom predicate which we are already using.

Expected: Beta 1

= docx,xslx,pptx MS Office XML compatability =

Upon upload of these file types EPrints 3.2 will automatically fill in much of the metadata such as title, authors and abstract if possible. 3.2 will also be able to pull these files apart offering optional access to the content within them such as embedded pictures.

Expected: Beta 1 (tentative)

= Enhancements to repository web site management =

Taking on the push of 3.1 to make it easy for the repository manager to edit and change the repository configuration without needing access to the configuration files themselves, we are taking that another step further. Coming in 3.2 we intend to allow full look and feel (branding) editing of the main EPrints web pages and templates to be done externally to EPrints in tools such Dreamweaver and Amaya. There will also be a complementary way of uploading new image files.

This editing capability is also complemented by two links which appear on certain pages enabling the administrator to directly edit the page look and feel as well as the phrases on that page.

Expected: Beta 1

= Abstract Page Improvements =

Lightboxes have been added to the abstract pages for easier previewing of documents.

Expected: Beta 1

= User definable datasets =

Allows you to expand the core EPrints data model with whole new types of data and datasets which can be indexed and used in searches. It is proposed that the stakeholders in the CERIF standard (projects, authors, institutions etc) will be modelled as separate EPrints datasets and used to support Research Management activities and integration with Research Information Systems.

Expected: Beta 1 (command line only)

= OAI-ORE Import and Export Plug-ins =

Capability to import and export resources or collections of resources as ORE Resource Maps. Both Atom and RDF serialisations are planned to be made available.

Expected: Beta 1

= IR Stats =

Institutional Repository stats are becoming an even more important part of the repository and we hope to have these in the final 3.2 release.

Expected: Beta 2

= EPrints Scheduler =

Allows tracking of events which happen as well as scheduling new events which need to take place to maintain your repository. Investigation is under way into the power of such a system and if it can be interfaced with desktop calendar programs such as iCal and Google Calendar.

Expected: Beta 2

= Shelves of EPrints =

No details to be released on this yet

Expected: Beta 2 (tentative)

= Coverpage capabilities =

Provides a mechanism for adding coverpages to documents before they are provided to users.

Expected: Beta 2 (tentative)

= Issues Raising and Resolving Tool =

No description currently

Expected: Beta 2 (tentative)

= Plugin system for document upload processing =

So zip,targz,file, from URL etc. become a plugin each and we add Docx/PPTx too.

Expected: Beta 1 (tentative)

= FTP and WebDAV Daemon Support =

Access to the user's inbox via FTP and WebDAV, allowing the repository to be mounted as a file system or network drive.

Expected: Beta 1 (tentative)

New Features in EPrints 3.2

2009-02-25T20:30:00Z

Lac: /* Thumbnails are now documents */

= EPrints Edit locking =

Allows you to lock editing to certain users and sessions (to make sure that two editors don't make simultaneous changes to the same record).

Expected: Beta 1

= Plug-in Based Storage Layer and Storage Controller =

The EPrints Storage Layer is evolving to enable easy plug-and-plug with many storage platforms including local and multiple institutional storage as well as cloud storage. The Storage Controller enables you to use multiple storage platforms simultaneously, define rules for what is stored on each platform and also manage these platforms and migrate resources between platforms as required. More information, including the current API, can be found on the [[StorageController]] page.

Expected: Beta 1

= Thumbnails are now documents =

Up to now, thumbnails have been 'special case' files that have not been managed very consistently by the repository. In particular, there has been no way to create or manage thumbnails through the API. Now, thumbnails and document previews are just documents of a specific type. This allows a much more flexible approach to be taken to thumbnails, with multiple size and multiple formats being acoomodated. It also becomes possible to have a different thumbnail for every slide in a PowerPoint slideshow, not just a thumbnail of the front slide. That in turn allows EPrints to potentially build visual catalogues of collections of PowerPoint presentations.

Expected: Beta 1

= SWORD 2 (1.3 Specification Support) =

Conforming to the new standards set out by the SWORD project, EPrints 3.2 will include compatibility for the new features.

Expected: Beta 1

= Preservation Planning Capabilities =

Allows EPrints to be linked with file classification tools (primarily DROID) and risk analysis services (PRONOM) which can then not only profile the content of your repository but also identify risks to objects contained within it.

More information on this can be found on the [[Preservation in EPrints 3.2]] page.

Expected: Beta 1

= Enhanced Compatability for DRIVER project systems =

In EPrints 3.2 repositories will be by default DREIVER enabled. In a future 3.1 release the better compatability will exist but will remain off by default.

Expected: EPrints 3.1 and 3.2.

= Arbitrary metadata linking capabilities =

Allows the user to expand their data model with custom predicates which link a resources with other resources. Such an example include the derivedFrom predicate which we are already using.

Expected: Beta 1

= docx,xslx,pptx MS Office XML compatability =

Upon upload of these file types EPrints 3.2 will automatically fill in much of the metadata such as title, authors and abstract if possible. 3.2 will also be able to pull these files apart offering optional access to the content within them such as embedded pictures.

Expected: Beta 1 (tentative)

= Enhancements to repository web site management =

Taking on the push of 3.1 to make it easy for the repository manager to edit and change the repository configuration without needing access to the configuration files themselves, we are taking that another step further. Coming in 3.2 we intend to allow full look and feel (branding) editing of the main EPrints web pages and templates to be done externally to EPrints in tools such Dreamweaver and Amaya. There will also be a complementary way of uploading new image files.

This editing capability is also complemented by two links which appear on certain pages enabling the administrator to directly edit the page look and feel as well as the phrases on that page.

Expected: Beta 1

= Abstract Page Improvements =

Lightboxes have been added to the abstract pages for easier previewing of documents.

Expected: Beta 1

= User definable datasets =

Allows you to expand the core EPrints data model with whole new types of data and datasets which can be indexed and used in searches. It is proposed that the stakeholders in the CERIF standard (projects, authors, institutions etc) will be modelled as separate EPrints datasets and used to support Research Management activities and integration with Research Information Systems.

Expected: Beta 1 (command line only)

= OAI-ORE Import and Export Plug-ins =

Capability to import and export resources or collections of resources as ORE Resource Maps. Both Atom and RDF serialisations are planned to be made available.

Expected: Beta 1

= IR Stats =

Institutional Repository stats are becoming an even more important part of the repository and we hope to have these in the final 3.2 release.

Expected: Beta 2

= EPrints Scheduler =

Allows tracking of events which happen as well as scheduling new events which need to take place to maintain your repository. Investigation is under way into the power of such a system and if it can be interfaced with desktop calendar programs such as iCal and Google Calendar.

Expected: Beta 2

= Shelves of EPrints =

No details to be released on this yet

Expected: Beta 2 (tentative)

= Coverpage capabilities =

Provides a mechanism for adding coverpages to documents before they are provided to users.

Expected: Beta 2 (tentative)

= Issues Raising and Resolving Tool =

No description currently

Expected: Beta 2 (tentative)

= Plugin system for document upload processing =

So zip,targz,file, from URL etc. become a plugin each and we add Docx/PPTx too.

Expected: Beta 1 (tentative)

= FTP and WebDAV Daemon Support =

Access to the user's inbox via FTP and WebDAV, allowing the repository to be mounted as a file system or network drive.

Expected: Beta 1 (tentative)

New Features in EPrints 3.2

2009-02-25T20:29:04Z

Lac: /* Thumbnails are now documents */

= EPrints Edit locking =

Allows you to lock editing to certain users and sessions (to make sure that two editors don't make simultaneous changes to the same record).

Expected: Beta 1

= Plug-in Based Storage Layer and Storage Controller =

The EPrints Storage Layer is evolving to enable easy plug-and-plug with many storage platforms including local and multiple institutional storage as well as cloud storage. The Storage Controller enables you to use multiple storage platforms simultaneously, define rules for what is stored on each platform and also manage these platforms and migrate resources between platforms as required. More information, including the current API, can be found on the [[StorageController]] page.

Expected: Beta 1

= Thumbnails are now documents =

Up to now, thumbnails have been 'special case' files that haven't been managed very consistently by the repository. In particular, there is no wau to create or manage thumbnails through the API. Now, thumbnails and document previews are just documents of a specific type. This allows a much more flexible approach to be taken to thumbnails, with multiple size and multiple formats being acoomodated. It also becomes possible to have a different thumbnail for every slide in a PowerPoint slideshow, not just a thumbnail of the front slide. That in turn allows EPrints to potentially build visual catalogues of collections of PowerPoint presentations.

Expected: Beta 1

= SWORD 2 (1.3 Specification Support) =

Conforming to the new standards set out by the SWORD project, EPrints 3.2 will include compatibility for the new features.

Expected: Beta 1

= Preservation Planning Capabilities =

Allows EPrints to be linked with file classification tools (primarily DROID) and risk analysis services (PRONOM) which can then not only profile the content of your repository but also identify risks to objects contained within it.

More information on this can be found on the [[Preservation in EPrints 3.2]] page.

Expected: Beta 1

= Enhanced Compatability for DRIVER project systems =

In EPrints 3.2 repositories will be by default DREIVER enabled. In a future 3.1 release the better compatability will exist but will remain off by default.

Expected: EPrints 3.1 and 3.2.

= Arbitrary metadata linking capabilities =

Allows the user to expand their data model with custom predicates which link a resources with other resources. Such an example include the derivedFrom predicate which we are already using.

Expected: Beta 1

= docx,xslx,pptx MS Office XML compatability =

Upon upload of these file types EPrints 3.2 will automatically fill in much of the metadata such as title, authors and abstract if possible. 3.2 will also be able to pull these files apart offering optional access to the content within them such as embedded pictures.

Expected: Beta 1 (tentative)

= Enhancements to repository web site management =

Taking on the push of 3.1 to make it easy for the repository manager to edit and change the repository configuration without needing access to the configuration files themselves, we are taking that another step further. Coming in 3.2 we intend to allow full look and feel (branding) editing of the main EPrints web pages and templates to be done externally to EPrints in tools such Dreamweaver and Amaya. There will also be a complementary way of uploading new image files.

This editing capability is also complemented by two links which appear on certain pages enabling the administrator to directly edit the page look and feel as well as the phrases on that page.

Expected: Beta 1

= Abstract Page Improvements =

Lightboxes have been added to the abstract pages for easier previewing of documents.

Expected: Beta 1

= User definable datasets =

Allows you to expand the core EPrints data model with whole new types of data and datasets which can be indexed and used in searches. It is proposed that the stakeholders in the CERIF standard (projects, authors, institutions etc) will be modelled as separate EPrints datasets and used to support Research Management activities and integration with Research Information Systems.

Expected: Beta 1 (command line only)

= OAI-ORE Import and Export Plug-ins =

Capability to import and export resources or collections of resources as ORE Resource Maps. Both Atom and RDF serialisations are planned to be made available.

Expected: Beta 1

= IR Stats =

Institutional Repository stats are becoming an even more important part of the repository and we hope to have these in the final 3.2 release.

Expected: Beta 2

= EPrints Scheduler =

Allows tracking of events which happen as well as scheduling new events which need to take place to maintain your repository. Investigation is under way into the power of such a system and if it can be interfaced with desktop calendar programs such as iCal and Google Calendar.

Expected: Beta 2

= Shelves of EPrints =

No details to be released on this yet

Expected: Beta 2 (tentative)

= Coverpage capabilities =

Provides a mechanism for adding coverpages to documents before they are provided to users.

Expected: Beta 2 (tentative)

= Issues Raising and Resolving Tool =

No description currently

Expected: Beta 2 (tentative)

= Plugin system for document upload processing =

So zip,targz,file, from URL etc. become a plugin each and we add Docx/PPTx too.

Expected: Beta 1 (tentative)

= FTP and WebDAV Daemon Support =

Access to the user's inbox via FTP and WebDAV, allowing the repository to be mounted as a file system or network drive.

Expected: Beta 1 (tentative)

New Features in EPrints 3.2

2009-02-25T19:58:04Z

Lac: /* EPrints Edit locking */

New Features in EPrints 3.2

2009-02-24T12:03:08Z

Lac: /* FTP and WebDAV Daemon Support */

= EPrints Edit locking =

Allows you to lock editing to certain users and sessions

Expected: Beta 1

= Plug-in Based Storage Layer and Storage Controller =

The EPrints Storage Layer is evolving to enable easy plug-and-plug with many storage platforms including local and multiple institutional storage as well as cloud storage. The Storage Controller enables you to use multiple storage platforms simultaneously, define rules for what is stored on each platform and also manage these platforms and migrate resources between platforms as required. More information, including the current API, can be found on the [[StorageController]] page.

Expected: Beta 1

= Thumbnails are now documents =

More details soon.

Expected: Beta 1

= SWORD 2 (1.3 Specification Support) =

Conforming to the new standards set out by the SWORD project, EPrints 3.2 will include compatibility for the new features.

Expected: Beta 1

= Preservation Planning Capabilities =

Allows EPrints to be linked with file classification tools (primarily DROID) and risk analysis services (PRONOM) which can then not only profile the content of your repository but also identify risks to objects contained within it.

More information on this can be found on the [[Preservation in EPrints 3.2]] page.

Expected: Beta 1

= Enhanced Compatability for DRIVER project systems =

In EPrints 3.2 repositories will be by default DREIVER enabled. In a future 3.1 release the better compatability will exist but will remain off by default.

Expected: EPrints 3.1 and 3.2.

= Arbitrary metadata linking capabilities =

Allows the user to expand their data model with custom predicates which link a resources with other resources. Such an example include the derivedFrom predicate which we are already using.

Expected: Beta 1

= docx,xslx,pptx MS Office XML compatability =

Upon upload of these file types EPrints 3.2 will automatically fill in much of the metadata such as title, authors and abstract if possible. 3.2 will also be able to pull these files apart offering optional access to the content within them such as embedded pictures.

Expected: Beta 1 (tentative)

= Enhancements to repository web site management =

Taking on the push of 3.1 to make it easy for the repository manager to edit and change the repository configuration without needing access to the configuration files themselves, we are taking that another step further. Coming in 3.2 we intend to allow full look and feel (branding) editing of the main EPrints web pages and templates to be done externally to EPrints in tools such Dreamweaver and Amaya. There will also be a complementary way of uploading new image files.

This editing capability is also complemented by two links which appear on certain pages enabling the administrator to directly edit the page look and feel as well as the phrases on that page.

Expected: Beta 1

= Abstract Page Improvements =

Lightboxes have been added to the abstract pages for easier previewing of documents.

Expected: Beta 1

= User definable datasets =

Allows you to expand the core EPrints data model with whole new types of data and datasets which can be indexed and used in searches. It is proposed that the stakeholders in the CERIF standard (projects, authors, institutions etc) will be modelled as separate EPrints datasets and used to support Research Management activities and integration with Research Information Systems.

Expected: Beta 1 (command line only)

= OAI-ORE Import and Export Plug-ins =

Capability to import and export resources or collections of resources as ORE Resource Maps. Both Atom and RDF serialisations are planned to be made available.

Expected: Beta 1

= IR Stats =

Institutional Repository stats are becoming an even more important part of the repository and we hope to have these in the final 3.2 release.

Expected: Beta 2

= EPrints Scheduler =

Allows tracking of events which happen as well as scheduling new events which need to take place to maintain your repository. Investigation is under way into the power of such a system and if it can be interfaced with desktop calendar programs such as iCal and Google Calendar.

Expected: Beta 2

= Shelves of EPrints =

No details to be released on this yet

Expected: Beta 2 (tentative)

= Coverpage capabilities =

Provides a mechanism for adding coverpages to documents before they are provided to users.

Expected: Beta 2 (tentative)

= Issues Raising and Resolving Tool =

No description currently

Expected: Beta 2 (tentative)

= Plugin system for document upload processing =

So zip,targz,file, from URL etc. become a plugin each and we add Docx/PPTx too.

Expected: Beta 1 (tentative)

= FTP and WebDAV Daemon Support =

Access to the user's inbox via FTP and WebDAV, allowing the repository to be mounted as a file system or network drive.

Expected: Beta 1 (tentative)

New Features in EPrints 3.2

2009-02-24T12:02:21Z

Lac: /* User definable datasets */

What Is EPrints

2008-04-27T23:10:38Z

Lac: /* Review */

Let's get away from the OAIS definitions and repository talk. Let's think about EPrints as an abstract information system. WHat features does it provide, so what classes of problem can it be used for?

== Acquisition ==
Perhaps primarily, EPrints is a tool for getting information from people. It has a very good interface (though we say so ourselves) for helping people enter quite complex information in as accurate and complete a way as possible, and it is very flexible about what kind of information can be entered and how.

You can use it for anything you want to capture from people: coursework handins, conference submissions, blog entries, summer holiday photo snaps, MP3 or video collections, questionnaires, workshop registration or credit card details. Or there's the more obvious repository candidates: scientific data, published documents, student portfolios, fine art exhibitions.

== Review ==
EPrints provides an editorial workflow for items that have been entered (see acquisition, above) to be checked, reviewed, commented on, modified, returned to the original depositor, moved to another reviewer, or placed into a final, published state. This facilitates simple peer review, editorial oversight or management authorisation for publishing, commentary or rights checking. EPrints has an extremely flexible editorial workflow that allows items that are requested for deposit to be passed to one or more editorial assistants, depending on the ''editorial scope'' that they have been assigned. Items can pass between different editors as different parts of the workflow are enacted. This means that a report can undergo copy-editing, copyright checks, IPR scrutiny and security analyses by a range of different people before it is allowed to appear in the public repository, or that a student PhD thesis can be signed off by the viva committee, the departmental teaching office and the library.

== Dissemination and Publishing ==
EPrints allows you to create and manage a large web site, with skins, a variety of navigation structures and search options, multilingual intefaces and adaptable content. The licensing and visibility of each item of content is controllable. This is great for all aspects of dissemination and publishing in the academic world. (We differentiate between the two because the items in the repository may have been ''published'' by a third party.)

As well as disseminating individual items, EPrints can deal with a set or collection of material. For example, it is an ideal place to put the proceedings from a conference or workshop, instead of creating a bare website from scratch. You can either set up a whole repository if it is a big conference (like [http://pubs.or08.ecs.soton.ac.uk/ Open Repositories 2008]) or just use a single collection if it is a small workshop (for example [http://journal.webscience.org/view/subjects/WE20081.html Web Evolve 2008]).

== Classification and Tagging ==
EPrints allows items to be tagged with controlled metadata from restricted vocabularies or taxonomies or with uncontrolled keywords or informal folksonomies. Its autocompletion facilities allow users to be [http://files.eprints.org/351/1/keyword-completion.png prompted with commonly used folk terms] to describe an item, and its keyword view styles [http://files.eprints.org/340/1/keyword-tagcloud.png allow tag clouds to be displayed].

== Ongoing Review Conditions ==
The manager-defined quality issues allow live items in the repository to be monitored against phases in their ongoing lifecycles. For example, to make sure that a record about a project has been updated with the completion report, or a submitted journal article has been updated with the decision to publish, or that a user has updated their CV in the last 6 months, or that the full set of referee's comments have been entered for a paper in a workshop.

== ITunes Interface ==
EPrints provides an ITunes-like, multicolumn interface for viewing selected attributes of a set of records taken from the repository. This allows an overall view of slices of the repository, and allows large numbers of records to be quickly compared and acted on. ''List some enabled use cases''

What Is EPrints

2008-04-27T23:10:19Z

Lac:

What Is EPrints

2008-04-27T23:09:22Z

Lac: /* ITunes Interface */

Let's get away from the OAIS definitions and repository talk. Let's think about EPrints as an abstract information system. WHat features does it provide, so what classes of problem can it be used for?

== Acquisition ==
Perhaps primarily, EPrints is a tool for getting information from people. It has a very good interface (though we say so ourselves) for helping people enter quite complex information in as accurate and complete a way as possible, and it is very flexible about what kind of information can be entered and how.

You can use it for anything you want to capture from people: coursework handins, conference submissions, blog entries, summer holiday photo snaps, MP3 or video collections, questionnaires, workshop registration or credit card details. Or there's the more obvious repository candidates: scientific data, published documents, student portfolios, fine art exhibitions.

== Review ==
EPrints provides an editorial workflow for items that have been entered (see acquisition, above) to be checked, reviewed, commented on, modified, returned to the original depositor, moved to another reviewer, or placed into a final, published state. This facilitates simple peer review, editorial oversight or management authorisation for publishing, commentary or rights checking.

== Dissemination and Publishing ==
EPrints allows you to create and manage a large web site, with skins, a variety of navigation structures and search options, multilingual intefaces and adaptable content. The licensing and visibility of each item of content is controllable. This is great for all aspects of dissemination and publishing in the academic world. (We differentiate between the two because the items in the repository may have been ''published'' by a third party.)

As well as disseminating individual items, EPrints can deal with a set or collection of material. For example, it is an ideal place to put the proceedings from a conference or workshop, instead of creating a bare website from scratch. You can either set up a whole repository if it is a big conference (like [http://pubs.or08.ecs.soton.ac.uk/ Open Repositories 2008]) or just use a single collection if it is a small workshop (for example [http://journal.webscience.org/view/subjects/WE20081.html Web Evolve 2008]).

== Classification and Tagging ==
EPrints allows items to be tagged with controlled metadata from restricted vocabularies or taxonomies or with uncontrolled keywords or informal folksonomies. Its autocompletion facilities allow users to be [http://files.eprints.org/351/1/keyword-completion.png prompted with commonly used folk terms] to describe an item, and its keyword view styles [http://files.eprints.org/340/1/keyword-tagcloud.png allow tag clouds to be displayed].

== Ongoing Review Conditions ==
The manager-defined quality issues allow live items in the repository to be monitored against phases in their ongoing lifecycles. For example, to make sure that a record about a project has been updated with the completion report, or a submitted journal article has been updated with the decision to publish, or that a user has updated their CV in the last 6 months, or that the full set of referee's comments have been entered for a paper in a workshop.

== ITunes Interface ==
EPrints provides an ITunes-like, multicolumn interface for viewing selected attributes of a set of records taken from the repository. This allows an overall view of slices of the repository, and allows large numbers of records to be quickly compared and acted on. ''List some enabled use cases''

== Editorial Workflow ==
EPrints has an extremely flexible editorial workflow that allows items that are requested for deposit to be passed to one or more editorial assistants, depending on the ''editorial scope'' that they have been assigned. Items can pass between different editors as different parts of the workflow are enacted. This means that a report can undergo copy-editing, copyright checks, IPR scrutiny and security analyses by a range of different people before it is allowed to appear in the public repository, or that a student PhD thesis can be signed off by the viva committee, the departmental teaching office and the library.

What Is EPrints

2008-04-27T22:54:09Z

Lac: /* Ongoing Review Conditions */

Let's get away from the OAIS definitions and repository talk. Let's think about EPrints as an abstract information system. WHat features does it provide, so what classes of problem can it be used for?

== Acquisition ==
Perhaps primarily, EPrints is a tool for getting information from people. It has a very good interface (though we say so ourselves) for helping people enter quite complex information in as accurate and complete a way as possible, and it is very flexible about what kind of information can be entered and how.

You can use it for anything you want to capture from people: coursework handins, conference submissions, blog entries, summer holiday photo snaps, MP3 or video collections, questionnaires, workshop registration or credit card details. Or there's the more obvious repository candidates: scientific data, published documents, student portfolios, fine art exhibitions.

== Review ==
EPrints provides an editorial workflow for items that have been entered (see acquisition, above) to be checked, reviewed, commented on, modified, returned to the original depositor, moved to another reviewer, or placed into a final, published state. This facilitates simple peer review, editorial oversight or management authorisation for publishing, commentary or rights checking.

== Dissemination and Publishing ==
EPrints allows you to create and manage a large web site, with skins, a variety of navigation structures and search options, multilingual intefaces and adaptable content. The licensing and visibility of each item of content is controllable. This is great for all aspects of dissemination and publishing in the academic world. (We differentiate between the two because the items in the repository may have been ''published'' by a third party.)

As well as disseminating individual items, EPrints can deal with a set or collection of material. For example, it is an ideal place to put the proceedings from a conference or workshop, instead of creating a bare website from scratch. You can either set up a whole repository if it is a big conference (like [http://pubs.or08.ecs.soton.ac.uk/ Open Repositories 2008]) or just use a single collection if it is a small workshop (for example [http://journal.webscience.org/view/subjects/WE20081.html Web Evolve 2008]).

== Classification and Tagging ==
EPrints allows items to be tagged with controlled metadata from restricted vocabularies or taxonomies or with uncontrolled keywords or informal folksonomies. Its autocompletion facilities allow users to be [http://files.eprints.org/351/1/keyword-completion.png prompted with commonly used folk terms] to describe an item, and its keyword view styles [http://files.eprints.org/340/1/keyword-tagcloud.png allow tag clouds to be displayed].

== Ongoing Review Conditions ==
The manager-defined quality issues allow live items in the repository to be monitored against phases in their ongoing lifecycles. For example, to make sure that a record about a project has been updated with the completion report, or a submitted journal article has been updated with the decision to publish, or that a user has updated their CV in the last 6 months, or that the full set of referee's comments have been entered for a paper in a workshop.

== ITunes Interface ==
EPrints provides an ITunes-like, multicolumn interface for viewing selected attributes of a set of records taken from the repository. This allows an overall view of slices of the repository, and allows large numbers of records to be quickly compared.

What Is EPrints

2008-04-27T22:47:47Z

Lac: /* Review Conditions */

Let's get away from the OAIS definitions and repository talk. Let's think about EPrints as an abstract information system. WHat features does it provide, so what classes of problem can it be used for?

== Acquisition ==
Perhaps primarily, EPrints is a tool for getting information from people. It has a very good interface (though we say so ourselves) for helping people enter quite complex information in as accurate and complete a way as possible, and it is very flexible about what kind of information can be entered and how.

You can use it for anything you want to capture from people: coursework handins, conference submissions, blog entries, summer holiday photo snaps, MP3 or video collections, questionnaires, workshop registration or credit card details. Or there's the more obvious repository candidates: scientific data, published documents, student portfolios, fine art exhibitions.

== Review ==
EPrints provides an editorial workflow for items that have been entered (see acquisition, above) to be checked, reviewed, commented on, modified, returned to the original depositor, moved to another reviewer, or placed into a final, published state. This facilitates simple peer review, editorial oversight or management authorisation for publishing, commentary or rights checking.

== Dissemination and Publishing ==
EPrints allows you to create and manage a large web site, with skins, a variety of navigation structures and search options, multilingual intefaces and adaptable content. The licensing and visibility of each item of content is controllable. This is great for all aspects of dissemination and publishing in the academic world. (We differentiate between the two because the items in the repository may have been ''published'' by a third party.)

As well as disseminating individual items, EPrints can deal with a set or collection of material. For example, it is an ideal place to put the proceedings from a conference or workshop, instead of creating a bare website from scratch. You can either set up a whole repository if it is a big conference (like [http://pubs.or08.ecs.soton.ac.uk/ Open Repositories 2008]) or just use a single collection if it is a small workshop (for example [http://journal.webscience.org/view/subjects/WE20081.html Web Evolve 2008]).

== Classification and Tagging ==
EPrints allows items to be tagged with controlled metadata from restricted vocabularies or taxonomies or with uncontrolled keywords or informal folksonomies. Its autocompletion facilities allow users to be [http://files.eprints.org/351/1/keyword-completion.png prompted with commonly used folk terms] to describe an item, and its keyword view styles [http://files.eprints.org/340/1/keyword-tagcloud.png allow tag clouds to be displayed].

== Ongoing Review Conditions ==
The manager-defined quality issues allow live items in the repository to be monitored against phases in their ongoing lifecycles. For example, to make sure that a record about a project has been updated with the completion report, or a submitted journal article has been updated with the decision to publish, or that a user has updated their CV in the last 6 months, or that the full set of referee's comments have been entered for a paper in a workshop.

What Is EPrints

2008-04-27T11:41:42Z