Help talk:Reference Tutorial - Revision history

Z8600021: /* PubmedParser */

2017-03-14T03:53:53Z

PubmedParser

← Older revision		Revision as of 13:53, 14 March 2017
Line 34:		Line 34:


	Steps for updating		Steps for updating from Pubmed to Parser extension code.

	# Open original page in edit mode.		# Open original page in edit mode.
	# In edit mode copy n paste into text editor.		# In edit mode copy n paste into text editor.

Z8600021: /* PubmedParser */

2017-03-14T03:53:26Z

PubmedParser

← Older revision		Revision as of 13:53, 14 March 2017
Line 32:		Line 32:

	Compared with the other, very useful extension Pubmed, this extension can be fully configured using Wiki messages (see the special page "Sytem Messages" in your wiki). It does not require editing configuration files on the server.		Compared with the other, very useful extension Pubmed, this extension can be fully configured using Wiki messages (see the special page "Sytem Messages" in your wiki). It does not require editing configuration files on the server.


			Steps for updating

			# Open original page in edit mode.
			# In edit mode copy n paste into text editor.
			# Find and replace <nowiki><pubmed></nowiki> with <nowiki>{{#pmid:PMIDno</nowiki>
			# Find and replace <nowiki></pubmed></nowiki> with <nowiki>}}</nowiki>
			# Copy n paste the new text back on the original page.
			# Save.

	===BiblioPlus===		===BiblioPlus===

Z8600021: /* PubMed Extensions */

2017-03-13T21:29:55Z

PubMed Extensions

← Older revision		Revision as of 07:29, 14 March 2017
Line 7:		Line 7:
	Need to test either PubmedParser or BiblioPlus as possible replacement.		Need to test either PubmedParser or BiblioPlus as possible replacement.


			===Pubmed===
			https://www.mediawiki.org/wiki/Extension:Pubmed

			The Pubmed extension can fetch literature data from scientific articles stored in PubMed (www.pubmed.org), and generate a reference list or box. The extension can create, in addition to the primary data like author, article title, journal, year, pages, etc., links like back to PubMed or to WorldCat.org by ISSN or to the full text at the publisher's page (if a DOI is specified). Further links can be defined using the layout template.

	[https://www.ncbi.nlm.nih.gov/books/NBK25497/ '''NCBI - Possible Blocking''']		[https://www.ncbi.nlm.nih.gov/books/NBK25497/ '''NCBI - Possible Blocking''']
Line 14:		Line 19:
	In order not to overload the E-utility servers, NCBI recommends that users post no more than three URL requests per second and limit large jobs to either weekends or between 9:00 PM and 5:00 AM Eastern time during weekdays. Failure to comply with this policy may result in an IP address being blocked from accessing NCBI. If NCBI blocks an IP address, service will not be restored unless the developers of the software accessing the E-utilities register values of the tool and email parameters with NCBI. The value of tool should be a string with no internal spaces that uniquely identifies the software producing the request. The value of email should be a complete and valid e-mail address of the software developer and not that of a third-party end user. The value of email will be used only to contact developers if NCBI observes requests that violate our policies, and we will attempt such contact prior to blocking access. In addition, developers may request that the value of email be added to the E-utility mailing list that provides announcements of software updates, known bugs and other policy changes affecting the E-utilities. To register tool and email values, simply send an e-mail to vog.hin.mln.ibcn@seitilitue including the desired values along with the name of either a developer or the organization creating the software. Once NCBI establishes communication with a developer, receives values for tool and email and validates the e-mail address in email, the block will be lifted. Once tool and email values are registered, all subsequent E-utility requests from that software package should contain both values. Please be aware that merely providing values for tool and email in requests is not sufficient to comply with this policy; these values must be registered with NCBI. Requests from any IP that lack registered values for tool and email and that violate the above usage policies may be blocked. Software developers may register values of tool and email at any time, and are encouraged to do so."		In order not to overload the E-utility servers, NCBI recommends that users post no more than three URL requests per second and limit large jobs to either weekends or between 9:00 PM and 5:00 AM Eastern time during weekdays. Failure to comply with this policy may result in an IP address being blocked from accessing NCBI. If NCBI blocks an IP address, service will not be restored unless the developers of the software accessing the E-utilities register values of the tool and email parameters with NCBI. The value of tool should be a string with no internal spaces that uniquely identifies the software producing the request. The value of email should be a complete and valid e-mail address of the software developer and not that of a third-party end user. The value of email will be used only to contact developers if NCBI observes requests that violate our policies, and we will attempt such contact prior to blocking access. In addition, developers may request that the value of email be added to the E-utility mailing list that provides announcements of software updates, known bugs and other policy changes affecting the E-utilities. To register tool and email values, simply send an e-mail to vog.hin.mln.ibcn@seitilitue including the desired values along with the name of either a developer or the organization creating the software. Once NCBI establishes communication with a developer, receives values for tool and email and validates the e-mail address in email, the block will be lifted. Once tool and email values are registered, all subsequent E-utility requests from that software package should contain both values. Please be aware that merely providing values for tool and email in requests is not sufficient to comply with this policy; these values must be registered with NCBI. Requests from any IP that lack registered values for tool and email and that violate the above usage policies may be blocked. Software developers may register values of tool and email at any time, and are encouraged to do so."

			* [https://www.ncbi.nlm.nih.gov/home/about/policies.shtml NCBI Website and Data Usage Policies and Disclaimers] possibly include this statement at the bottom of reference lists?


	~~===Pubmed===~~
	~~https://www.mediawiki.org/wiki/Extension:Pubmed~~

	The Pubmed extension can fetch literature data from scientific articles stored in PubMed (www.pubmed.org), and generate a reference list or box. The extension can create, in addition to the primary data like author, article title, journal, year, pages, etc., links like back to PubMed or to WorldCat.org by ISSN or to the full text at the publisher's page (if a DOI is specified). Further links can be defined using the layout template.

	===PubmedParser===		===PubmedParser===

Z8600021: /* PubMed Extensions */

2017-03-13T21:27:19Z

PubMed Extensions

← Older revision		Revision as of 07:27, 14 March 2017
Line 8:		Line 8:


	* [https://www.ncbi.nlm.nih.gov/books/NBK25497/ NCBI - Possible Blocking]		[https://www.ncbi.nlm.nih.gov/books/NBK25497/ '''NCBI - Possible Blocking''']

			"Frequency, Timing and Registration of E-utility URL Requests

			In order not to overload the E-utility servers, NCBI recommends that users post no more than three URL requests per second and limit large jobs to either weekends or between 9:00 PM and 5:00 AM Eastern time during weekdays. Failure to comply with this policy may result in an IP address being blocked from accessing NCBI. If NCBI blocks an IP address, service will not be restored unless the developers of the software accessing the E-utilities register values of the tool and email parameters with NCBI. The value of tool should be a string with no internal spaces that uniquely identifies the software producing the request. The value of email should be a complete and valid e-mail address of the software developer and not that of a third-party end user. The value of email will be used only to contact developers if NCBI observes requests that violate our policies, and we will attempt such contact prior to blocking access. In addition, developers may request that the value of email be added to the E-utility mailing list that provides announcements of software updates, known bugs and other policy changes affecting the E-utilities. To register tool and email values, simply send an e-mail to vog.hin.mln.ibcn@seitilitue including the desired values along with the name of either a developer or the organization creating the software. Once NCBI establishes communication with a developer, receives values for tool and email and validates the e-mail address in email, the block will be lifted. Once tool and email values are registered, all subsequent E-utility requests from that software package should contain both values. Please be aware that merely providing values for tool and email in requests is not sufficient to comply with this policy; these values must be registered with NCBI. Requests from any IP that lack registered values for tool and email and that violate the above usage policies may be blocked. Software developers may register values of tool and email at any time, and are encouraged to do so."

Z8600021: /* PubMed Extensions */

2017-03-13T21:26:19Z

PubMed Extensions

← Older revision		Revision as of 07:26, 14 March 2017
Line 6:		Line 6:

	Need to test either PubmedParser or BiblioPlus as possible replacement.		Need to test either PubmedParser or BiblioPlus as possible replacement.


			* [https://www.ncbi.nlm.nih.gov/books/NBK25497/ NCBI - Possible Blocking]


	===Pubmed===		===Pubmed===

Z8600021 at 23:15, 19 Ocak 2017

2017-01-19T23:15:12Z

← Older revision		Revision as of 09:15, 20 Ocak 2017
Line 4:		Line 4:

	Note there is a update to PHP7 pending in 2017.		Note there is a update to PHP7 pending in 2017.

			Need to test either PubmedParser or BiblioPlus as possible replacement.

	===Pubmed===		===Pubmed===
Line 12:		Line 14:
	===PubmedParser===		===PubmedParser===
	https://www.mediawiki.org/wiki/Extension:PubmedParser		https://www.mediawiki.org/wiki/Extension:PubmedParser

			https://github.com/bovender/PubmedParser/

	4.0.1 (2016-11-09)		4.0.1 (2016-11-09)
Line 18:		Line 22:

	Compared with the other, very useful extension Pubmed, this extension can be fully configured using Wiki messages (see the special page "Sytem Messages" in your wiki). It does not require editing configuration files on the server.		Compared with the other, very useful extension Pubmed, this extension can be fully configured using Wiki messages (see the special page "Sytem Messages" in your wiki). It does not require editing configuration files on the server.

			===BiblioPlus===
			https://www.mediawiki.org/wiki/Extension:BiblioPlus

			===ProcessCite===

			https://www.mediawiki.org/wiki/Extension:ProcessCite

	==Pubget==		==Pubget==

Z8600021 at 22:59, 19 Ocak 2017

2017-01-19T22:59:09Z

← Older revision		Revision as of 08:59, 20 Ocak 2017
Line 1:		Line 1:
			==PubMed Extensions==

			Currently using Pubmed extension, but this has not been maintained and has begun generating errors at the server end.

			Note there is a update to PHP7 pending in 2017.

			===Pubmed===
			https://www.mediawiki.org/wiki/Extension:Pubmed

			The Pubmed extension can fetch literature data from scientific articles stored in PubMed (www.pubmed.org), and generate a reference list or box. The extension can create, in addition to the primary data like author, article title, journal, year, pages, etc., links like back to PubMed or to WorldCat.org by ISSN or to the full text at the publisher's page (if a DOI is specified). Further links can be defined using the layout template.

			===PubmedParser===
			https://www.mediawiki.org/wiki/Extension:PubmedParser

			4.0.1 (2016-11-09)

			The PubmedParser extension provides a parser keyword (#pmid) to fetch article information by unique ID from the Pubmed database. It outputs the article information formatted as Wiki markup for a template. The template can be defined inside the Wiki and adjusted as needed.

			Compared with the other, very useful extension Pubmed, this extension can be fully configured using Wiki messages (see the special page "Sytem Messages" in your wiki). It does not require editing configuration files on the server.

	==Pubget==		==Pubget==
	http://corporate.pubget.com/ipad		http://corporate.pubget.com/ipad

Z8600021 at 05:21, 29 November 2012

2012-11-29T05:21:18Z

← Older revision		Revision as of 15:21, 29 November 2012
Line 1:		Line 1:
			==Pubget==
			http://corporate.pubget.com/ipad

	==Simple Referencing==		==Simple Referencing==

Z8600021 at 02:50, 19 October 2012

2012-10-19T02:50:02Z

← Older revision		Revision as of 12:50, 19 October 2012
Line 4:		Line 4:

	PMID 18508724		PMID 18508724


	~~<pubmed>induced stem cell</pubmed>~~

Z8600021: /* Simple Referencing */

2012-10-19T02:49:37Z

Simple Referencing

← Older revision		Revision as of 12:49, 19 October 2012
Line 6:		Line 6:


	<pubmed>~~Human Zygote~~</pubmed>		<pubmed>induced stem cell</pubmed>