Publications Committee Minutes - 2018 Virtual Meeting

From Wess

(Difference between revisions)
Jump to: navigation, search
 
Line 39: Line 39:
<li>Content is stored on google</li>
<li>Content is stored on google</li>
<li>Jon has had issued with being locked out of Google Sites in the past.</li></ul>
<li>Jon has had issued with being locked out of Google Sites in the past.</li></ul>
-
Wordpress – this is sort of a moot point—if ALA offers Wordpress integration, there’s no reason to go out on our own
+
Wordpress – this is sort of a moot point—if ALA offers Wordpress integration, there’s no reason to go out on our own<br/>
-
Stacks – CMS sold by EBSCO  
+
Stacks – CMS sold by EBSCO  
-
o Expensive, but is primarily designed for libraries rather than smaller organizations like this
+
<ul><li>Expensive, but is primarily designed for libraries rather than smaller organizations like this</li></ul>
-
Squarespace – variety of options and templates available               
+
Squarespace – variety of options and templates available<br/>                
-
o Example: http://www.hacken.org/
+
<ul><li>Example: http://www.hacken.org/</li></ul>
-
o Funds come from ACRL—we’re pretty close to our fund limit, but we do have generous donors
+
Discussion points
-
Membership survey will be conducted soon, which includes questions about how the website is used
+
<ul><li>Funds come from ACRL—we’re pretty close to our fund limit, but we do have generous donors.</li>
-
Where should the money be spent? Is the maintenance cost more important, or is money to redesign the website more important?  
+
<li>Membership survey will be conducted soon, which includes questions about how the website is used</li>
-
DECISION : Brian will draft questions to pass to ALA / ACRL and will contact them as the preferred option for the website going forward.
+
<li>Where should the money be spent? Is the maintenance cost more important, or is money to redesign the website more important?</li>
-
Exec will continue with survey as it is in order to see how membership uses the website. Survey will be open for approximately 1 month, and will go out soonish
+
<li><strong>DECISION : Brian will draft questions to pass to ALA / ACRL and will contact them as the preferred option for the website going forward.</strong></li>
-
Further discussion/meetings will be required to come up with plan for what to do with content and how to transfer it.
+
<li>Exec will continue with survey as it is in order to see how membership uses the website. Survey will be open for approximately 1 month, and will go out soonish.</li>
 +
<li>Further discussion/meetings will be required to come up with plan for what to do with content and how to transfer it.</li></ul>

Latest revision as of 20:20, 7 June 2019

Website Task Force of ESS Publications Commmittee Virtual Meeting | November 6, 2018

MINUTES

Attendees: Jon Giullian, Dick Hacken, Josh Hutchinson (minutes), Adrienne Seely, Ann Snoeyenbos (ESS Chair) Brian Vetruba (ESS Publications Chair), Michelle Urberg


Website Task Force -- background - When WESS and SEES merged, in the merger agreement, it was decided to figure out the best way to let the 2 websites exist for a while, and then work out the options for eventually merging the websites or leaving them or some other option
- Presenting options to the executive about options—both for the hosting solution and for the desired situation (ie, 1 website, 2, etc)
- Second task force is looking at the publications (newsletter and journal)
- Members of the task force have looked at vendors
- Current WESS website has some voluminous resource guides, which will/would require significant work transferring (including links out to historic newsletters from the 1970s onwards)

There is a Google spreadsheet with our notes about the vendors we’re looking at. Presentation of findings for the six vendors:

ACRL
  • no cost, no limit to data/document storage, section will need to do most of transferring of content, can be either wordpress (acrl.ala.org/IS) or a template from ALA, libguides is also an option—ALA has a subscription
  • Multiple editors isn’t a problem; maybe could put business content on wordpress, other content on libguides
  • Some pages currently exist that are access restricted—new host will need to allow that as well.
  • Is there a collaborative workspace as part of the Wordpress system? Or will ALA Connect need to be used? If so, that would mean three systems are used
  • ACTION: Brian will contact the Instruction section and get feedback from them about their current use of the ALA Wordpress sites.
Siteground
  • have had trouble with bandwidth, server that allows use of various platforms including wiki, wordpress and Joomla capabilities
  • Requires credit card on file, no Section credit card, so chair’s private credit card is often the easiest solution for allowing this to work
  • Can link out to
  • No collaborative workspace available
  • Content from SEES website will need to be integrated into Siteground if we stay with existing site—transferring content will still be required (though there will still be less required)
  • Would be possible to add additional Siteground hosted wikis to include (e.g.) SEES material

Further discussion about use of Wiki sites -- https://www.vanhamel.nl/codecs/Home uses MediaWiki with a skin called Chameleon

Google
  • provide services for non-profits (with provision of a non-profit number)
  • We have never purchased custom URL, which can be done through URL (eccslavic.org uses a google site with a custom URL which redirects to https://sites.google.com/site/eccslavic/) but this would require a credit card
  • Multiple editors is very easy—adding additional managers is simply adding new email addresses
  • Can be a challenge to achieve standardization in look and feel
  • Ease of use and multi-editors is easy—designed to work more functionally with mobile devices; took some time to get used to editing and working with the site
  • Biggest problem is storage—limit on storage (unlimited for gsuite business or education (and for non-profits?))
  • Content is stored on google
  • Jon has had issued with being locked out of Google Sites in the past.

Wordpress – this is sort of a moot point—if ALA offers Wordpress integration, there’s no reason to go out on our own
Stacks – CMS sold by EBSCO

  • Expensive, but is primarily designed for libraries rather than smaller organizations like this

Squarespace – variety of options and templates available

Discussion points

  • Funds come from ACRL—we’re pretty close to our fund limit, but we do have generous donors.
  • Membership survey will be conducted soon, which includes questions about how the website is used
  • Where should the money be spent? Is the maintenance cost more important, or is money to redesign the website more important?
  • DECISION : Brian will draft questions to pass to ALA / ACRL and will contact them as the preferred option for the website going forward.
  • Exec will continue with survey as it is in order to see how membership uses the website. Survey will be open for approximately 1 month, and will go out soonish.
  • Further discussion/meetings will be required to come up with plan for what to do with content and how to transfer it.
Personal tools