User:Ckeene/Ideas for future versions of eprints - Revision history

Pm705 at 16:03, 8 February 2010

2010-02-08T16:03:00Z

← Older revision		Revision as of 16:03, 8 February 2010
Line 1:		Line 1:
			[[Category:Feedback]]
	'''''Disclaimer: I know the eprints team is small, doing very cool stuff, have lots of ideas of their own and, of course, eprints is free! This is all just 'what I would like to see', while appreciating that these things may not be coming any time soon, or are not the direction the rest of the eprints community want to go in.'''''		'''''Disclaimer: I know the eprints team is small, doing very cool stuff, have lots of ideas of their own and, of course, eprints is free! This is all just 'what I would like to see', while appreciating that these things may not be coming any time soon, or are not the direction the rest of the eprints community want to go in.'''''

Ckeene at 16:18, 3 July 2008

2008-07-03T16:18:39Z

← Older revision		Revision as of 16:18, 3 July 2008
Line 1:		Line 1:
			'''''Disclaimer: I know the eprints team is small, doing very cool stuff, have lots of ideas of their own and, of course, eprints is free! This is all just 'what I would like to see', while appreciating that these things may not be coming any time soon, or are not the direction the rest of the eprints community want to go in.'''''

	== Long term : fit in with academic workflow ==		== Long term : fit in with academic workflow ==
	Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)		Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)

Ckeene: /* One Repository, multiple views (long term?) */

2008-07-03T16:10:46Z

One Repository, multiple views (long term?)

← Older revision		Revision as of 16:10, 3 July 2008
Line 57:		Line 57:

	* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]		* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]
			* CJK July 2008: looks like 3.1 will have the option of additional templates. http://wiki.eprints.org/w/New_Features_in_EPrints_3.1#Templates a good start (though still think there is more scope here and so leaving this on this list, for example the idea that someone could go to eprints.uni.edu/etheses/ and search/browse just theses in a completely different looking system and when they click on deposit see a different set of fields customised for thesis submission).

	== Auto LOC classify ==		== Auto LOC classify ==

Ckeene: added youtube embedded player idea

2008-07-03T16:06:33Z

added youtube embedded player idea

← Older revision		Revision as of 16:06, 3 July 2008
Line 91:		Line 91:
	These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)		These are just my personal thoughts, partly based on feedback we've received from academics. Though the last idea was mainly due to Citeseer making documents availabele in many formats (e.g. http://citeseer.ist.psu.edu/lagoze01open.html)
	Like I say, these are all non-trivial, but hope it makes for good food for thought!		Like I say, these are all non-trivial, but hope it makes for good food for thought!

			== Youtube style embedded player for video/av items ==
			We want to encourage people to upload av and video research/teaching content. If they upload it to youtube (or the million other clone services) it looks cool. If they upload it to eprints, it looks like a file icon.

			Feature: a plugin to alter the abstract pages of multimedia content to have an embeded (flash) player similar to youtube.

			(July 2008)


	== Things that have made it in to Eprints 3.1 ==		== Things that have made it in to Eprints 3.1 ==

Lac: /* Long term : fit in with academic workflow */

2008-04-19T12:01:21Z

Long term : fit in with academic workflow

← Older revision		Revision as of 12:01, 19 April 2008
Line 2:		Line 2:
	Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)		Academics make funding bids, do research, etc, then write a draft article, then submit to journal(s), get published. (actually I don't really have a clue what academics do, but hopefully this is a good guess!)

	* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is.'' [LES CARR]		* ''All of these are examples of creating documents and revising documents and sharing documents. This isn't too far from what a repository is. We have thought about helping integrate with the desktop by supporting WebDAV.'' [LES CARR]

	At the moment we 'bolt on' to the end of this, but what if we could play a bigger role.		At the moment we 'bolt on' to the end of this, but what if we could play a bigger role.

Lac: /* Auto LOC classify */

2008-04-19T10:08:07Z

Auto LOC classify

← Older revision		Revision as of 10:08, 19 April 2008
Line 64:		Line 64:
	If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).		If there was some way eprints could use some web based service to find a suitable LOC heading to suggest to the user, based on the journal/book title. (i.e. if there is a web service that can be passed a title or issn/isbn and return a LOC heading for that journal/book).

			* ''We attempted this in an old JISC Project called "EPrints UK" using Dewey instead of LOC, but it relied on an experimental service from OCLC. If anyone could point us at such a service for LoC we would happily use it! '' [LES CARR]

	== Auto submit to other repositories ==		== Auto submit to other repositories ==

Lac: /* One Repository, multiple views (long term?) */

2008-04-19T10:05:25Z

One Repository, multiple views (long term?)

← Older revision		Revision as of 10:05, 19 April 2008
Line 55:		Line 55:

	Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!		Of course '''some''' of this is technically possible (creating a search form which only searchers certain criteria or creating extra browse views), but I think a more comprehensive approach could have some potential. I guess what I am saying is that to all intents and purposes, the public and users would see two (or more) sperate repositories, but behind the scenes is just one. In fact, situations like the Soton/ECS dual setup could potentially be nicely accommodated with this!

			* ''There is a general issue of making special collections a lot easier to manage, and that is something that we are working on. (That will support research groups and journals as well as scholarly collections.) However the issue of allowing groups to have their own listings on their own pages is often better supported by allowing them to import blank (unbranded) listings from the repository which are then branded by the local site using stylesheets. This puts control of the department/research group's pages into their hands, which makes them happy.'' [LES CARR]

	== Auto LOC classify ==		== Auto LOC classify ==

Lac: /* Enhance the eprint abstract page (a la flickr) */

2008-04-19T09:59:07Z

Enhance the eprint abstract page (a la flickr)

← Older revision		Revision as of 09:59, 19 April 2008
Line 38:		Line 38:
	== Enhance the eprint abstract page (a la flickr) ==		== Enhance the eprint abstract page (a la flickr) ==
	the Eprints team briefly demonstrated this at OR08. It looked great.		the Eprints team briefly demonstrated this at OR08. It looked great.

			* ''Here's a mockup [http://users.ecs.soton.ac.uk/jtp/projects/ePrints/index4.html Abstract page]'' [LES CARR]

	Basically two things:		Basically two things:

Lac: /* Enhance the concept of authors (and editors) */

2008-04-19T09:40:36Z

Enhance the concept of authors (and editors)

← Older revision		Revision as of 09:40, 19 April 2008
Line 33:		Line 33:

	Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.		Having an 'object' for authors would allow, for example, one REAL Author to have multiple display names, so that if one paper has them down as "C Keene" and another as "Prof C.J.Keene" eprints can still treat them as the same person, even if they show up differently on different papers. It allows for clever things, like allowing other systems to have a list of one person's research (not just research that so happens to have the same name attached to it, how many John Smiths work at your Uni?). And perhaps in the future it would allow 'Authors' (not just depositors) to login and see everything of theirs in the repository (everything they have co-authors, not just deposited) and 'do stuff with it'.

			* ''But you can already do all these things. That's why we have ids attached to authors, not just their names. You can View by Author IDs, and produce complete lists of an individual's research. As you point out there are USER objects which you could provide a bigger role for, beyond identifying the depositor as they do now.'' [LES CARR]

	== Enhance the eprint abstract page (a la flickr) ==		== Enhance the eprint abstract page (a la flickr) ==

Lac: /* Allow users to be authenticated by an external system */

2008-04-19T09:37:31Z

Allow users to be authenticated by an external system

← Older revision		Revision as of 09:37, 19 April 2008
Line 18:		Line 18:
	E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.		E.g. when authentication is needed, the user is redirected to a predefined webpage (probably on the Institutions website) which handles login, and can pass back to eprints a successful login and the username of the user who has logged in.

			* ''I think this is already what we do with eprints.ecs, as al authentication is handled by a single login page. I will check with Chris'' [LES CARR]

	This is a little similar to what ezproxy can do		This is a little similar to what ezproxy can do
Line 23:		Line 24:
	and also, in a way, to how shibboleth works.		and also, in a way, to how shibboleth works.

	The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!).		The advantage is that it would allow a wide variety of campus authentication systems to be used to authenticate eprints, and eprints does not need to worry about handling password (and being secure with them, which is a key issue!).

	== Enhance the concept of authors (and editors) ==		== Enhance the concept of authors (and editors) ==