Changes

Jump to: navigation, search

FCIG Report

1,733 bytes added, 21:35, 25 January 2018
m
sub-heading disambiguation
Code4Lib Fiscal Continuity Interest Group Report
23 January 2017, updated on 11 19 September 2017
== A. Executive Summary ==
2. LITA/ALA
===== Proposed Terms for Fiscal Sponsorship , LITA/ALA =====
The Library Information Technology Association (LITA), a division of the American Library Association (ALA), is willing to serve as a fiscal agent for the Code4Lib conference on either a short-term or long-term basis. There are two models under which this could happen:
4. CLIR/DLF
===== Proposed Terms for Fiscal Sponsorship , CLIR/DLF =====
The Council on Library and Information Resources, the parent organization of the Digital Library Federation, has also offered possible terms for providing ongoing fiscal sponsorship for Code4Lib. The terms outlined below were discussed via email and phone conversations with Bethany Nowviskie, Director, DLF, and Sharon Ivy Weiss, Chief Operating Officer, CLIR, between October-December 2016. In these conversations, the FCIG provided via email an adaptation of the list of questions Coral prepared for potential sponsors (as discussed with LITA/ALA, outlined above). Quotations below are taken from emails written by Bethany Nowviskie in response to these questions, and are used with her permission.
=== Table: Summary of Options ===
<This table> <tr> <td>Option</td> <td>Cost required to implement</td> <td>Other costs/ recurring costs?</td> <td>Any required changes to Code4Lib conference- planning process?</td> <td>Any required changes to Code4Lib organizational structure?</td> <td>Does this provide ongoing gives only a broad comparison of the options. For fuller details on the points summarized below, please see the individual sections for each of the potential fiscal host for Code4Lib conference?</td> </tr> <tr> <td>Fiscal sponsorshipsponsors: LITA/ALA</td> <td>26.4% of gross revenue</td> <td></td> <td>Coordination with LITA/ALA</td> <td>Primary conference organizers would need to hold LITA membership; would need process to identify primary contact to LITA/ALA</td> <td>yes</td> </tr> <tr> <td>Fiscal sponsorship: CLIR/DLF</td> <td>$5,000 / year</td> <td>$5,000 / year to Code4Lib nest egg account</td> <td>CLIR/DLF would not require changes; Code4Lib would need to continue hiring conference mgmt services. CLIR/DLF recommends event insurance.</td> <td>Would need process to identify primary contact to CLIR/DLF</td> <td>yes</td> </tr> <tr> <td>Code4Lib forms NPO</td> <td>$2,000 to $8OLF,000 to form</td> <td>$1and DuraSpace,000 to $2and the sections presenting the requirements involved in forming a non-profit organization option,000 in filing fees</td> <td>Potential need to secure legal services to review contracts.</td> <td>Election of the board (or setting up board to include all Code4Lib members) and election of officers</td> <td>yes</td> </tr> <tr> <td>Maintain as well as maintaining status quo</td> <td>0</td> <td>Ongoing liability burdens on host institutions</td> <td>no</td> <td>no</td> <td>no</td> </tr></table>.
{|
!Option
!Cost required to implement
!Other costs/ recurring costs?
!Any required changes to Code4Lib conference- planning process?
!Any required changes to Code4Lib organizational structure?
!Does this provide ongoing fiscal host for Code4Lib conference?
|-
|Fiscal sponsorship: LITA/ALA
|26.4% of gross revenue
|
|Coordination with LITA/ALA
|Primary conference organizers would need to hold LITA membership; would need process to identify primary contact to LITA/ALA
|yes
|-
|Fiscal sponsorship: CLIR/DLF
|$5,000 / year
|$5,000 / year to Code4Lib nest egg account
|CLIR/DLF would not require changes; Code4Lib would need to continue hiring conference mgmt services. CLIR/DLF recommends event insurance.
|No change to current C4L culture would be necessary. CLIR/DLF is fine with C4L’s current practice of local organizing committees and rotating leadership for the conference and other activities. CLIR/DLF requests only that C4L would identify current points of contact for each activity such as conference, listserv, website, etc.
|yes
|-
|Fiscal sponsorship: Open Library Federation
|To be determined, in coordination with OLF
|Needs to be determined: whether OLF or C4L would cover event insurance cost annually
|OLF did not specify any required changes to the conference planning process
|OLF requires member communities to have explicit governance that is documented in a charter or similar instrument
|yes
|-
|Fiscal sponsorship: DuraSpace
|$7,000 / year
|DuraSpace recommends C4L create &amp; maintain a reserve account of $75Kto cover at minimum half of the cost of potential conference failure, and to purchase event insurance for annual conference
|DuraSpace would not require changes, but strongly recommends C4L obtain event insurance for annual conference
|DuraSpace requests C4L identify leadership with authorization: to sign Memorandum of Understanding (MOU), and to spend C4L funds; also expects C4L to report expenses and revenues annually
|yes, with qualification regarding shared coverage of potential conference failure
|-
|Code4Lib forms NPO
|$2,000 to $8,000 to form
|$1,000 to $2,000 in filing fees
|Potential need to secure legal services to review contracts.
|Election of the board (or setting up board to include all Code4Lib members) and election of officers
|yes
|-
|Maintain status quo
|0
|Ongoing liability burdens on host institutions
|no
|no
|no
|}
=== Option 1: Maintain the status quo ===
=== Option 2: obtain ongoing fiscal sponsorship from an external organization ===
 
In this Report, the terms specified for each of the organizations identified as possible fiscal sponsors provide an outline of the requirements and benefits of ongoing fiscal sponsorship with a host organization. This analysis is meant to inform a Code4Lib community vote among the three broad options presented in this Report (1: maintain status quo, 2: obtain ongoing fiscal sponsorship, or 3: form an independent non-profit organization), as well as to provide a basis for comparison between the possible terms offered by each of the organizations within Option 2.
====== Pros: Possible Benefits of an Ongoing, Long-term fiscal sponsor for Code4Lib ======
10
edits

Navigation menu