519
edits
Difference between revisions of "Content team"
Jump to navigation
Jump to search
→Scraping
| (8 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
== Responsabilities == | == Responsabilities == | ||
* | * Content Requests | ||
** Collaborate with requesters to qualify requests properly. Keep them informed. | ** Collaborate with requesters to qualify requests properly. Keep them informed. | ||
** Ensure we are allowed and able to fullfill requests | ** Ensure we are allowed and able to fullfill requests | ||
| Line 30: | Line 30: | ||
** Ensure ZIM are recent and kept up2date (AFAP) | ** Ensure ZIM are recent and kept up2date (AFAP) | ||
** Ensure library is coherent and user-friendly | ** Ensure library is coherent and user-friendly | ||
== Policies == | |||
=== Publishing === | |||
* Content has to be legal in Switzerland | |||
* Content should not advertise [https://en.wikipedia.org/wiki/Fringe_theory fringe theory] | |||
* Content should betterne [https://en.wikipedia.org/wiki/Free_content free content] | |||
* If not free, content should be: | |||
** Open content OR | |||
** Educational content OR | |||
** has an authorization of reproduction | |||
* Any content we publish should | |||
** have (almost) no user visible error | |||
** have proper/correct metadata | |||
** be easily discoverable in the public library | |||
=== Content Requests === | |||
* Allow everybody to request new, changes or deletion of content | |||
* In full transparency track the lifecycle of our content portfolio | |||
* New content should be assessed and vetted content against publishing policy (see above) | |||
* Content requests should be closed: | |||
** when fully implemented (user visible) | |||
** if refusal or impossibility of implementation | |||
* ZIM Medata should be given for new content | |||
* Only once all prerequisites are satisfied, then start with scraping | |||
=== Scraping === | |||
* Scraping leadership means the initiative should come from the content team | |||
* First analysis of error should be done by content team | |||
* If error in scraper is suspected | |||
** Issue should be updated to corresponding scraper code repository | |||
** Scraper problem analysis does not super-seed in any manner content request | |||
* ZIM quality should be vetted against publishing policy | |||
* Any recipe should run successfully first in dev before been put in production | |||
* Hardware resources should be saved | |||
=== Library Management === | |||
== Processes == | |||
=== Content Requests === | |||
=== Scraping === | |||
=== Library Management === | |||
== Worflows == | |||
== Members == | == Members == | ||