Empowering Italian GLAMs/Tech evaluations

Da Wikimedia Italia.
Jump to navigation Jump to search

Information about the tool related to Empowering Italian GLAMs.

Specifications

Domain
To be identified.
Command line access
Should be not required.
User storage needed
30G (1000 musei, 20 foto, 1.5M/foto)
Dependencies
* PHP (executes Python commands)
* MySQL database
* Python
Available servers
  • Cloud VPS: to be requested
    m:wikitech:Wikitech:Cloud Services Terms of use
  • server from current provider 💼 vh - average cost max. 400€ / server, automated backups already included
  • lessema: enough storage but it's dedicated to CiviCRM - not enough separation
  • beta: not owned by WMIT
  • delta: not owned by WMIT
  • epsilon: not owned by WMIT
  • horror: dedicated to backups - not enough separation
  • intreccio: not enough storage
  • manoscritto: not enough storage - not enough separation with ZNUNY
  • toolforge: not enough storage - https://t.me/wmcloudirc/44175

Questions from Cloud VPS activists

About unclear copyright status files on Wikimedia Cloud servers
<bozzy> there is a person who verifies a scanned piece of paper in which a museum manager authorizes the release in free license, before uploading on Commons.
<bozzy> This way the Commons community does not receive an avalanche of problematic data. We felt it was more respectful to them.
[29/08/22 17:10]
<taavi> you can't store material with unclear copyright status on WMCS either..
About uploading directly on Commons
<bozzy> The tool will be a sort of "image uploader". Kind of "pre-Commons" for a GLAM-related project in a specific country.
[29/08/22 17:00]
<bd808_> Why not upload to commons and then mark the "unuseful" things for deletion? Commons will have more storage and better performance than almost any Cloud VPS project.
<bd808> https://commons.wikimedia.org/wiki/Commons:Volunteer_Response_Team is exactly for things like reviewing and validating image releases as well. I'm not saying I know enough to say that there is no need for a staging process, but this all sounds like things that the community knows how to deal with.

Team

Developer
Voluntary consultation