2013Q1 Reports: Info Officer - Revision history

Min-YenKan at 09:11, 4 March 2013

2013-03-04T09:11:52Z

← Older revision		Revision as of 09:11, 4 March 2013
Line 139:		Line 139:
	We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster, either by using the hosting package or by using a public free mail system (Yahoo! mail, Google Groups). I believe Drago is currently ok with the system he is using to manage the multiple sources for mailing lists.		We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster, either by using the hosting package or by using a public free mail system (Yahoo! mail, Google Groups). I believe Drago is currently ok with the system he is using to manage the multiple sources for mailing lists.

	== Future Plans ==		== Future Plans - IMPORTANT FOR ACL EXEC CONFERENCE CALL ==
	This is an area where I need more feedback from the ACL Exec about what we'd like to see as an organization. I'll briefly outline my two most urgent perspectives (aside from the maintenance problems aforementioned).		This is an area where I need more feedback from the ACL Exec about what we'd like to see as an organization. I'll briefly outline my two most urgent perspectives (aside from the maintenance problems aforementioned).

Line 176:		Line 176:
	Funding for the IO responsibilities: While the webmaster / portal are paid positions, we don't have any staff that are paid for the development of the Anthology. I think we should consider adding this to the Portal or Webmaster responsibility (to be directed by the IO). Information services cost the ACL a small but constant amount of funding. But further development by grassroot initiatives (AAN, Searchbench, Saffron) need to be funded to have long-term sustainability for our membership. We could seek corporate sponsorship of the Anthology's maintenance, if the Exec feel that this is appropriate way to lessen costs (we have started to ask whether certain commercial entities who traditionally sponsor ACL events would be interested).		Funding for the IO responsibilities: While the webmaster / portal are paid positions, we don't have any staff that are paid for the development of the Anthology. I think we should consider adding this to the Portal or Webmaster responsibility (to be directed by the IO). Information services cost the ACL a small but constant amount of funding. But further development by grassroot initiatives (AAN, Searchbench, Saffron) need to be funded to have long-term sustainability for our membership. We could seek corporate sponsorship of the Anthology's maintenance, if the Exec feel that this is appropriate way to lessen costs (we have started to ask whether certain commercial entities who traditionally sponsor ACL events would be interested).

	The ACL Exec should consider two proposals about important, long-term publishing properties: DOI and long term archiving ~~via CLOCKSS~~. The first is more important. Currently Digital Object Identifiers (DOIs) are assigned to our materials by the ACM, under the agreement of our ACL-ACM agreement negotiated previously by Steven Bird. The prior agreement gives ACM the right to register DOIs for our materials (and thus the right for		The ACL Exec should consider two proposals about important, long-term publishing properties: DOI and long term archiving. The first is more important. Currently Digital Object Identifiers (DOIs) are assigned to our materials by the ACM, under the agreement of our ACL-ACM agreement negotiated previously by Steven Bird. The prior agreement gives ACM the right to register DOIs for our materials (and thus the right for
	the DOIs to resolve to the ACM Portal) in exchange for paying the necessary fees (US $1 per article/publication). With TACL coming up as a journal, it will be important for ACL to establish itself as a DOI assigner. Taking charge of our own DOIs also will allow us to print the DOIs on proceedings before being published. The downside is the cost. To assign DOIs to scholarly articles, the standard registration agency is CrossRef. Their annual fee is $275, and an additional $1 per registered item. Since ACL and its associated workshops generate about 2000 proceedings per year, it would cost between 2-3K per year to allow us to assign DOIs. As ACL Anthology Editor, I think the presence of TACL may better motivate our own need to register as a DOI provider with CrossRef (note: I have briefly corresponded with Michael and Dekang about TACL registering DOIs, they are interested but not aware of the process or costs, to my understanding).		the DOIs to resolve to the ACM Portal) in exchange for paying the necessary fees (US $1 per article/publication). With TACL coming up as a journal, it will be important for ACL to establish itself as a DOI assigner. Taking charge of our own DOIs also will allow us to print the DOIs on proceedings before being published. The downside is the cost. To assign DOIs to scholarly articles, the standard registration agency is CrossRef. Their annual fee is $275, and an additional $1 per registered item. Since ACL and its associated workshops generate about 2000 proceedings per year, it would cost between 2-3K per year to allow us to assign DOIs. As ACL Anthology Editor, I think the presence of TACL may better motivate our own need to register as a DOI provider with CrossRef (note: I have briefly corresponded with Michael and Dekang about TACL registering DOIs, they are interested but not aware of the process or costs, to my understanding).

	For long term archiving, the CLOCKSS initiative is a non-profit organization that keeps copies of digital materials for archiving in case a publisher goes away. This is less important since the Anthology was conceived for just this purpose. Currently, I would not recommend subscription for this. Costs for this service currently are US $200 per year and $0.25 per object to be archived. This would amount to about $1K per year. I can investigate this further if needed.		For long term archiving, the CLOCKSS initiative is a non-profit organization that keeps copies of digital materials for archiving in case a publisher goes away. This is less important since the Anthology was conceived for just this purpose. Currently, I would not recommend subscription for this. Costs for this service currently are US $200 per year and $0.25 per object to be archived. This would amount to about $1K per year. I can investigate this further if needed.

Min-YenKan: /* Future Plans */

2013-03-04T09:10:57Z

Future Plans

← Older revision		Revision as of 09:10, 4 March 2013
Line 172:		Line 172:
	* elections (Min: ?)		* elections (Min: ?)
	* ACL answers (e.g. StackExchange like site) - (long term)		* ACL answers (e.g. StackExchange like site) - (long term)


			Funding for the IO responsibilities: While the webmaster / portal are paid positions, we don't have any staff that are paid for the development of the Anthology. I think we should consider adding this to the Portal or Webmaster responsibility (to be directed by the IO). Information services cost the ACL a small but constant amount of funding. But further development by grassroot initiatives (AAN, Searchbench, Saffron) need to be funded to have long-term sustainability for our membership. We could seek corporate sponsorship of the Anthology's maintenance, if the Exec feel that this is appropriate way to lessen costs (we have started to ask whether certain commercial entities who traditionally sponsor ACL events would be interested).

			The ACL Exec should consider two proposals about important, long-term publishing properties: DOI and long term archiving via CLOCKSS. The first is more important. Currently Digital Object Identifiers (DOIs) are assigned to our materials by the ACM, under the agreement of our ACL-ACM agreement negotiated previously by Steven Bird. The prior agreement gives ACM the right to register DOIs for our materials (and thus the right for
			the DOIs to resolve to the ACM Portal) in exchange for paying the necessary fees (US $1 per article/publication). With TACL coming up as a journal, it will be important for ACL to establish itself as a DOI assigner. Taking charge of our own DOIs also will allow us to print the DOIs on proceedings before being published. The downside is the cost. To assign DOIs to scholarly articles, the standard registration agency is CrossRef. Their annual fee is $275, and an additional $1 per registered item. Since ACL and its associated workshops generate about 2000 proceedings per year, it would cost between 2-3K per year to allow us to assign DOIs. As ACL Anthology Editor, I think the presence of TACL may better motivate our own need to register as a DOI provider with CrossRef (note: I have briefly corresponded with Michael and Dekang about TACL registering DOIs, they are interested but not aware of the process or costs, to my understanding).

			For long term archiving, the CLOCKSS initiative is a non-profit organization that keeps copies of digital materials for archiving in case a publisher goes away. This is less important since the Anthology was conceived for just this purpose. Currently, I would not recommend subscription for this. Costs for this service currently are US $200 per year and $0.25 per object to be archived. This would amount to about $1K per year. I can investigate this further if needed.

Min-YenKan: /* Anthology */

2013-03-04T09:04:22Z

Anthology

← Older revision		Revision as of 09:04, 4 March 2013
Line 24:		Line 24:
	The new ACL Anthology has gone live in Feb 2012. Unfortunately, due to a number of maintainer problems, the system has not been live for very long. It is an important part of the Anthology work to have the new version be stable, up-and-running on a constant basis for 2013.		The new ACL Anthology has gone live in Feb 2012. Unfortunately, due to a number of maintainer problems, the system has not been live for very long. It is an important part of the Anthology work to have the new version be stable, up-and-running on a constant basis for 2013.

	We have also gotten the Exec's approval to use a separate domain (aclanthology.info) and hosting company (Amazon EC2) for the service.		We have also gotten the Exec's approval to use a separate domain (aclanthology.info) and hosting company (Amazon EC2) for the service. This service is not yet active.

	With respect to materials, we continue to integrate other CL related venues into the Anthology to increase the prestige of ACL as well as to make the Anthology even more useful. We have integrated TALN (in French) and RANLP (English) over the last period.		With respect to materials, we continue to integrate other CL related venues into the Anthology to increase the prestige of ACL as well as to make the Anthology even more useful. We have integrated TALN (in French) and RANLP (English) over the last period.

Min-YenKan: /* Future Plans */

2013-03-04T09:03:17Z

Future Plans

← Older revision		Revision as of 09:03, 4 March 2013
Line 148:		Line 148:
	Drago also maintained a wish list of things related to information services. I've tried to format his list to cluster several parts together. I confess I don't completely understand what all of the topics mean. I hope to be able to review these with all of you in the conference call, so that we can prioritize what are the issues that need to be addressed.		Drago also maintained a wish list of things related to information services. I've tried to format his list to cluster several parts together. I confess I don't completely understand what all of the topics mean. I hope to be able to review these with all of you in the conference call, so that we can prioritize what are the issues that need to be addressed.

	Anthology ~~issues~~:		Anthology:
	* links to Google Scholar, ArnetMiner, ACL Author Network		* links to Google Scholar, ArnetMiner, ACL Author Network
	* similar people to me (using ACL Anthology)		* similar people to me (using ACL Anthology)
Line 158:		Line 158:
	* taxonomy of NLP topics - (long term)		* taxonomy of NLP topics - (long term)

	Portal/Website ~~issues~~:		Portal/Website:
	* SIG membership		* SIG membership
	* volunteering intentions		* volunteering intentions
	* reviewing availability DB		* reviewing availability DB (Min: would this really be used by members and kept updated?)
	* integration with TACL		* integration with TACL (Min: ?)
	* integration with conf. content		* integration with conf. content (Min: ?)

	Wiki:		Wiki:
	* all ACL rules, etc.		* all ACL rules, etc.
	* submissions dates		* submissions dates (Min: for conferences?)
	* opt out		* opt out (Min: ?)
	* ACL fellows		* ACL fellows (Min: ?)
	* elections		* elections (Min: ?)
	* ACL answers (e.g. StackExchange like site) - (long term)		* ACL answers (e.g. StackExchange like site) - (long term)

Min-YenKan: /* Future Plans */

2013-03-04T09:02:04Z

Future Plans

← Older revision		Revision as of 09:02, 4 March 2013
Line 145:		Line 145:

	'''Sponsorship.''' A long term goal that I'd like to introduce is to get much of the costs of the IO portfolio to be self-sustaining. This means that the corporate interests in CL/NLP help to defray the costs of not only conferences but the Anthology, its sister projects and the website as well. A coordinated plan will involve our rotating conferences (for example, the conferences could contribute some funds for the running of the website and Anthology on a per-article basis).		'''Sponsorship.''' A long term goal that I'd like to introduce is to get much of the costs of the IO portfolio to be self-sustaining. This means that the corporate interests in CL/NLP help to defray the costs of not only conferences but the Anthology, its sister projects and the website as well. A coordinated plan will involve our rotating conferences (for example, the conferences could contribute some funds for the running of the website and Anthology on a per-article basis).

			Drago also maintained a wish list of things related to information services. I've tried to format his list to cluster several parts together. I confess I don't completely understand what all of the topics mean. I hope to be able to review these with all of you in the conference call, so that we can prioritize what are the issues that need to be addressed.

			Anthology issues:
			* links to Google Scholar, ArnetMiner, ACL Author Network
			* similar people to me (using ACL Anthology)
			* software to comment on papers
			* video recordings
			* slides
			* past tutorials and workshops
			* showcasing IE/Bib software - (long term)
			* taxonomy of NLP topics - (long term)

			Portal/Website issues:
			* SIG membership
			* volunteering intentions
			* reviewing availability DB
			* integration with TACL
			* integration with conf. content

			Wiki:
			* all ACL rules, etc.
			* submissions dates
			* opt out
			* ACL fellows
			* elections
			* ACL answers (e.g. StackExchange like site) - (long term)

Min-YenKan: /* Mailing Lists */

2013-03-04T08:55:02Z

Mailing Lists

← Older revision		Revision as of 08:55, 4 March 2013
Line 137:		Line 137:
	== Mailing Lists ==		== Mailing Lists ==

	We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster, either by using the hosting package or by using a public free mail system (Yahoo! mail, Google Groups)		We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster, either by using the hosting package or by using a public free mail system (Yahoo! mail, Google Groups). I believe Drago is currently ok with the system he is using to manage the multiple sources for mailing lists.

	~~'''Action Items~~.~~'''~~ ~~Check~~ with ~~secretary~~ to ~~see how this should be handled~~.

	== Future Plans ==		== Future Plans ==

Min-YenKan: /* Executive Summary */

2013-03-04T08:52:37Z

Executive Summary

← Older revision		Revision as of 08:52, 4 March 2013
Line 3:		Line 3:
	=== Executive Summary ===		=== Executive Summary ===

	The IO portfolio includes integration of the different ACL-wide ~~(exclusive of SIGs)~~ activities that are related to information dissemination; including the Anthology, website, wiki, portal and archive. Plans include short-term goals to provide integration of back-end resources (mailing lists), updating of software installations; mid-term goals of central-sign in for ACL services; and long-term goals for the costs of the information services to be sponsored and absorbed by corporate interests.		The IO portfolio includes integration of the different ACL-wide activities that are related to information dissemination; including the Anthology, website, wiki, portal and archive. Plans include short-term goals to provide integration of back-end resources (mailing lists), updating of software installations; mid-term goals of central-sign in for ACL services; and long-term goals for the costs of the information services to be sponsored and absorbed by corporate interests.

	=== Presumed duties ===		=== Presumed duties ===

Min-YenKan at 08:58, 14 February 2013

2013-02-14T08:58:09Z

← Older revision		Revision as of 08:58, 14 February 2013
Line 141:		Line 141:
	'''Action Items.''' Check with secretary to see how this should be handled.		'''Action Items.''' Check with secretary to see how this should be handled.

	== ~~Sponsorship~~ ==		== Future Plans ==
			This is an area where I need more feedback from the ACL Exec about what we'd like to see as an organization. I'll briefly outline my two most urgent perspectives (aside from the maintenance problems aforementioned).

	A long term goal that I'd like to introduce is to get much of the costs of the IO portfolio to be self-sustaining. This means that the corporate interests in CL/NLP help to defray the costs of not only conferences but the Anthology, its sister projects and the website as well. A coordinated plan will involve our rotating conferences (for example, the conferences could contribute some funds for the running of the website and Anthology on a per-article basis).		'''Single-sign On.''' We can utilize OpenID and other technologies (ORCID, meant for uniquely identifying research authors) to allow our members to use their Google, FaceBook, LinkedIn or other account to login to the portal, anthology (and eventually START). Having a single convenient method for sign-on will hopefully boost uptake and continued servicing of member accounts.

			'''Sponsorship.''' A long term goal that I'd like to introduce is to get much of the costs of the IO portfolio to be self-sustaining. This means that the corporate interests in CL/NLP help to defray the costs of not only conferences but the Anthology, its sister projects and the website as well. A coordinated plan will involve our rotating conferences (for example, the conferences could contribute some funds for the running of the website and Anthology on a per-article basis).

Min-YenKan at 08:53, 14 February 2013

2013-02-14T08:53:22Z

← Older revision		Revision as of 08:53, 14 February 2013
Line 140:		Line 140:

	'''Action Items.''' Check with secretary to see how this should be handled.		'''Action Items.''' Check with secretary to see how this should be handled.

			== Sponsorship ==

			A long term goal that I'd like to introduce is to get much of the costs of the IO portfolio to be self-sustaining. This means that the corporate interests in CL/NLP help to defray the costs of not only conferences but the Anthology, its sister projects and the website as well. A coordinated plan will involve our rotating conferences (for example, the conferences could contribute some funds for the running of the website and Anthology on a per-article basis).

Min-YenKan at 08:49, 14 February 2013

2013-02-14T08:49:58Z

← Older revision		Revision as of 08:49, 14 February 2013
Line 137:		Line 137:
	== Mailing Lists ==		== Mailing Lists ==

	We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster.		We keep organizational mailing lists as part of the secretary's post. However, our webhosting package allows for the construction of mailing lists. We may want to assess whether we'd like to offload this responsibility to the webmaster, either by using the hosting package or by using a public free mail system (Yahoo! mail, Google Groups)

	'''Action Items.''' Check with secretary to see how this should be handled.		'''Action Items.''' Check with secretary to see how this should be handled.