HughP / olac

Automatically exported from code.google.com/p/olac
0 stars 0 forks source link

OLAC Quarterly Report #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Set up OLAC Quarterly Report to use quarterly data from Google Analytics,
and make sure the cron job sends it out quarterly.

Original issue reported on code.google.com by StevenBird1 on 19 Dec 2008 at 9:17

GoogleCodeExporter commented 9 years ago

Original comment by garyfsim...@gmail.com on 19 Dec 2008 at 9:20

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Matthew will need to change the timing of the weekly GA email reports to 
monthly.

Original comment by StevenBird1 on 2 Jan 2009 at 8:26

GoogleCodeExporter commented 9 years ago
The subject line of the quarterly report emails should no longer include 
"testing"

Original comment by StevenBird1 on 2 Jan 2009 at 8:32

GoogleCodeExporter commented 9 years ago
Also, reports for archives that haven't been updated for many months weren't 
generated because of a missing function: addMonths().

Original comment by haepal on 2 Jan 2009 at 10:55

GoogleCodeExporter commented 9 years ago
Changed it to monthly. GA will send it on the first day of each month. This may 
mess 
up the data for January 2009. It could double count the hits for the first 4 
days as 
they were included in a weekly report. Easy to fix if it's a problem.

Original comment by salutmathieu@gmail.com on 8 Jan 2009 at 11:18

GoogleCodeExporter commented 9 years ago
Pretty much done. What's remaining:

(1) Four sites haven't received the report. Can we send it now?

(2) Haejoong will update the GA processing script once the first monthly report 
is
received.

Original comment by haepal on 26 Jan 2009 at 8:41

GoogleCodeExporter commented 9 years ago
Yes, please go ahead with (1).

Original comment by StevenBird1 on 26 Jan 2009 at 10:55

GoogleCodeExporter commented 9 years ago
Messages bounced for: SCOIL, DOBES, AILLA, ELRA, Kayardild (reported by Debbie 
to Gary).

Original comment by StevenBird1 on 26 Jan 2009 at 11:02

GoogleCodeExporter commented 9 years ago
From Debbie Chang:

Here is a summary of the bouncing e-mail addresses and their archives.
Five
out of six of these e-mail addresses have been recorded as bouncing since
November of 2007, and I had deleted them from the OLAC-IMPLEMENTERS list.
Baden Hughes's e-mail address is the newly bouncing one.

<ailla@ailla.org>                    Archive of the Indigenous Languages of
Latin
America
                        I assume Heidi Johnson is still involved with this
archive,
and that her email address, hjohnson@MAIL.UTEXAS.EDU, is still good.

<olac-admin@inalf.fr>          ATILF Resources
                        I do not know of another e-mail addresses for this
archive.

<freddy.offenga@mpi.nl>        DOBES catalogue - OLAC 1.0
                        Paul Trilsbeek at dobes@mpi.nl is the other
contact for this
archive.

<mapelli@elda.fr>                    European Language Resources
Association
                        I do not know of any other e-mail addresses for
this
archive.

<lbwelch@uclink.berkeley.edu>        Survey for California and Other Indian
Languages
                        Leanne Hinton hinton@socrates.berkeley.edu and
Lisa Conathan
conathan@CALMAIL.BERKELEY.EDU are additional contacts for this archive.

<badenh@CS.MU.OZ.AU>           Virtual Kayardild Archive
                        Baden Hughes has another e-mail address listed
with this
archive: baden@compuling.net

Original comment by StevenBird1 on 26 Jan 2009 at 11:04

GoogleCodeExporter commented 9 years ago
[#8] Sent quarterly reports for the following archives:

    83 crdo.up.univ-aix.fr (CRDO Archive)
    89 mbcarrom.linguistlist.org (Magoria Books' Carib and Romani Archive)
    90 talkbank.org (TALKBANK Data Repository)
    92 www.ldc.upenn.edu (The LDC Corpus Catalog)

Issues on archives with bouncing emails will still have to be resolved. Is 
there a
way to check availability of email address? Also, is there an automatic way to 
check
the status of report deliveries?

Original comment by haepal on 29 Jan 2009 at 8:28

GoogleCodeExporter commented 9 years ago
I don't think there's any way to deal with this automatically.  The from 
address should be set so that a human 
receives any bounces.  Perhaps we should have a mail alias as the from address.

Original comment by StevenBird1 on 29 Jan 2009 at 10:28

GoogleCodeExporter commented 9 years ago
The processing scripts for Google Analytics reports have been updated (#7).

To summarize the timings, the report arrives on the first of every month. The 
processing script processes the report on the second day of the month. The 
quarterly 
reports are sent out on the third day of January, April, July and October.

Original comment by haepal on 3 Feb 2009 at 6:41

GoogleCodeExporter commented 9 years ago
Need to verify that this worked, on April 4.

Original comment by StevenBird1 on 13 Mar 2009 at 8:53

GoogleCodeExporter commented 9 years ago

Original comment by haepal on 30 Apr 2009 at 3:47

GoogleCodeExporter commented 9 years ago

Original comment by StevenBird1 on 24 Mar 2010 at 1:35