You are not logged in.

[Testing] LTI System Manager

  • "Di Anna" is female

Posts: 870

Date of registration: Jun 12th 2011

Language Team: ENGLISH

Focus Group: English Proofreader
Final Reviewer

Location: Efland, NC

Thanks: 30423 / 980

  • Send private message

76

Wednesday, April 3rd 2013, 1:25am

Thanks, Ray,
Good points, on both counts!
How's this?

Hello Vixi,

You have been invited to join us at Linguistic Team International as we work together 'translating to change the world'.
Please, go to our PMS to have access to all our material.

http://pms.linguisticteam.org

Your username is: vixi@teamling.com
Your password is: lti

We strongly recommend you change the password FIRST. Then complete your profile so we can get to know you better. Be sure to introduce yourself to the Team in the Thread under Help Desk, and find your Language Team Coordinator on Wiki. Then take some time to explore the Forum and have fun getting to know our Community.

Welcome to Linguistic Team International.
Signature from »Di Anna« Important: The forum can send you an email for each post that you are interested in.
Please follow these directions to adjust your settings so that you receive communications.

1 registered user and 53 guests thanked already.

Users who thanked for this post:

Ray

  • "Ray" is male

Posts: 1,592

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 50847 / 7318

  • Send private message

77

Thursday, April 4th 2013, 9:17am

Much better.
The only thing I would change is the reference to the wiki for them to find their team coord. We're taking a different approach now, having the coords meet the person in the forum instead of disappearing into the abyss somewhere else. So, just leave off that part and it seems perfect to me. :rose:
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

1 registered user and 51 guests thanked already.

Users who thanked for this post:

Di Anna

  • "Di Anna" is female

Posts: 870

Date of registration: Jun 12th 2011

Language Team: ENGLISH

Focus Group: English Proofreader
Final Reviewer

Location: Efland, NC

Thanks: 30423 / 980

  • Send private message

78

Thursday, April 4th 2013, 2:33pm

Hello Vixi,

You have been invited to join us at Linguistic Team International as we work together 'translating to change the world'.
Please, go to our PMS to have access to all our material.

http://pms.linguisticteam.org

Your username is: vixi@teamling.com
Your password is: lti

We strongly recommend you change the password FIRST. Then complete your profile so we can get to know you better. Be sure to introduce yourself to the Team in the Thread under Help Desk. Then take some time to explore the Forum and have fun getting to know our Community.

Welcome to Linguistic Team International.


How's that, Maestro! :loveya:
Di
Signature from »Di Anna« Important: The forum can send you an email for each post that you are interested in.
Please follow these directions to adjust your settings so that you receive communications.

2 registered users and 52 guests thanked already.

Users who thanked for this post:

Ray, Yayita

  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

79

Sunday, April 14th 2013, 7:57pm

It took me days but I finally update the PMS:

http://www.timelinguistico.com.br/ltipms/

user: admin@lti.com
pass: lti

I believe we don't need to add new features here and now we can just focus on finding bugs. Maybe I will create a 'checklist' to help testing the system.
Please, create some users and add some new videos. Test it a lot. :)

When everybody agree that we have a stable version then we are ready to move forward with the PMS.

Hugs! :bighug:

4 registered users and 47 guests thanked already.

Users who thanked for this post:

nomada, Di Anna, Ray, Yayita

Posts: 3,052

Date of registration: May 24th 2011

Language Team: English

Focus Group: Timestamp Adjustment Team
Public Relations Group

Location: Malmö, Sweden

Thanks: 93177 / 2397

  • Send private message

80

Sunday, April 14th 2013, 11:03pm

Let's clean these cocaroachas amigos! :fc-spy:
Shall we have a session together and go through the whole system in a more systematic approach, or everyone just surprises de bugs any day/time of the week so we catch them distracted?
Signature from »nomada« Click to know how to: - Receive email notifications - Join the LTI biweekly Meetings

3 registered users and 39 guests thanked already.

Users who thanked for this post:

Di Anna, Ray, Yayita

  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

81

Monday, April 15th 2013, 1:41am

hahaha :rofl:

I think in the future I can create a 'checklist' of testing... I mean, a document that contains all the different items that must be tested, step by step. I think that will be helpful and more systematic, as you said.
But for now everybody can go into the system, create some users and some videos and test the hell of it. :fc-pirate:

Of course, if you guys want to create that checklist already, please, go ahead. Maybe I will need to be offline for a few days cause my client is asking for her system.

You can report bugs here or in our github repository: https://github.com/linguisticteam/ltipms/issues


See ya! :fc-bye-bye:

5 registered users and 52 guests thanked already.

Users who thanked for this post:

nomada, Di Anna, Ray, Yayita, kwizrak

  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

82

Monday, April 22nd 2013, 2:36am

Diomides Skalistis posted many relevant issues on Facebook. Here is the list:


The list is a bit long so I beg for your patience and understanding. In each issue I write if it is a bug or enhancement. Also in some cases I'll expand a bit more. Everything is my opinion and should be considered that way, even if it seems like a "must do" phrasing. The order is as they came to my mind
1) Ability to see the all the members as Menu item and not clicking on the menu title (Members).
I think this would be more easy for people. I didn't catch it right away and if I hadn't seen the video, I probably should wonder about it.
Enhancement

2) Locations must be mandatory
Enhancement

3) A star should be added at mandatory field descriptions
Enhancement

4) In Video Edit when adding someone that have contributed to a category (eg Translator) with the second option (someone that is not a member of the PMS)
a) If later on such a member subscribes then the star is not removed. It should.
b) If the member name has spaces then it displays as %20%. If selected from the existing members list it displays fine
c) If the member has non-English characters (eg Greek) then it displays as a series of ASCII characters ie %nn%nn%nn%nn%nn...%nn%, where n is a number. If selected from the existing members list it displays fine
Enhancement

5) When adding a member the ability to change his role and status should be available.
Enhancement

6) If we think of adding the ability to Add Videos to other teams, then the a field "Spoken Language" or something like that should be created in the Add Video page.
Enhancement

7) "Add a new team page" should be available at Administrators.
Enhancement

Date Checking.
Start Date <= Today
Published Date => Start Date
Published Date <= Today
Bug

9) In Member Edit there should be an option to delete a member from the team in the Coordinator's menus.
Enhancement

10) When sending invitations 2 messages arrive.
Bug

11) What is the "waiting for confirmation" status?
Question

12) Adding a member should create the invite message automatically. Request for confirmation/create account in that mail and when the account is done the status of the member should become automatically active. Inactive should be only in the judgement of the Coord.
Enhancement

13) Invitation message should be editable by coord. There may be some standards which they may not be altered but the coord should have the ability to add more info to the message concering his/her team (facebook pages, local youtubes, etc)
Enhancement

14) In Edit Video steps should be in dropdown list as they do not "affect" other parts. If we think that an automatic message should be sent eg to all timestamp adjusters then it has a meaning. Only the last one should remain as is and lock the video. Same and in Edit Video for all Teams except English
Enhancement

15) The button in Edit Video should say "Done" or "Save Changes"
Enhancement

16) The button in Add Member should say "Add"
Enhancement

17) The button in Edit Member should say "Done" or "Save Changes"
Enhancement

18) Where exactly do we use the publish link?
Question

19) What is the difference with Repository Storage and Repository Location?
Question

20) if error in Adding a video (eg the mail does not contain a @) then the category and priority are reset. These should remain as selected by the user
Enhancement

21) A popup baloon would help in each step explaining everything that is needed. Otherwise a help button or something similar must be created.
Enhancement

22) The step definition and the menu under "Videos" should match. Otherwise there is a confusion
Enhancement

23) Somewhere there should be an option to view all videos.
Enhancement

24) After the video is locked, the Englidh team has the ability to change it. All these information (Locations, Description, Category) should pass to all teams. This doesn't happen.
Bug

25) After adding someone as a contributor in the video (eg Add Ray as a Transcriber) the screen goes to the top. It should remain in the same position if the user want to add more people
Enhancement

52 guests thanked already.
  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

83

Friday, April 26th 2013, 9:35pm

Ok people... that's important because it's an important step and I your help here.

That is the database of language teams.


CREATE TABLE IF NOT EXISTS `pms_language_teams` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(45) NOT NULL,
`shortname` varchar(45) NOT NULL,
`description` varchar(255) NOT NULL,
`youtube_channel` varchar(255) NOT NULL,
`facebook_group` varchar(255) NOT NULL,
`facebook_page` varchar(255) NOT NULL,
`twitter` varchar(45) NOT NULL,
`homepage` varchar(255) NOT NULL,
`forum_playground` varchar(255) NOT NULL,
`team_permissions` tinyint(4) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `shortname` (`shortname`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

And above we have the list of teams we will have. Please, confirm if this database is the same from dotsub languages.

Is that correct? Do we have to add more columns?



INSERT INTO `pms_language_teams` (`id`, `team_name`) VALUES
(1, 'English'),
(2, 'Abkhaz'),
(3, 'Achenese'),
(4, 'Acoli'),
(5, 'Adygei'),
(6, 'Afar'),
(7, 'Afrihili'),
(8, 'Afrikaans'),
(9, 'Afro-Asiatic'),
(10, 'Ainu'),
(11, 'Akan'),
(12, 'Akkadian'),
(13, 'Albanian'),
(14, 'Aleut'),
(15, 'Algonquian'),
(16, 'Southern Altai'),
(17, 'Altaic'),
(18, 'Amharic'),
(19, 'Angika'),
(20, 'Apache'),
(21, 'Arabic'),
(22, 'Aragonese'),
(23, 'Aramaic'),
(24, 'Arapao'),
(25, 'Arawak'),
(26, 'Armenian'),
(27, 'Artificial'),
(28, 'Assamese'),
(29, 'Asturian'),
(30, 'Athapascan'),
(31, 'Austronesian'),
(32, 'Avaric'),
(33, 'Avestan'),
(34, 'Awadhi'),
(35, 'Aymara'),
(36, 'Azerbaijani'),
(37, 'Balinese'),
(38, 'Baltic'),
(39, 'Baluchi'),
(40, 'Bambara'),
(41, 'Bamileke'),
(42, 'Banda'),
(43, 'Bantu'),
(44, 'Basa'),
(45, 'Bashkir'),
(46, 'Basque'),
(47, 'Batak'),
(48, 'Bedawi'),
(49, 'Belarusian'),
(50, 'Bemba'),
(51, 'Bengali'),
(52, 'Berber'),
(53, 'Bhojpuri'),
(54, 'Bihari'),
(55, 'Bicolano'),
(56, 'Bilen'),
(57, 'Bislama'),
(58, 'Siksika'),
(59, 'Blissymbols'),
(60, 'Bosnian'),
(61, 'Braj Bhasha'),
(62, 'Breton'),
(63, 'Buginese'),
(64, 'Bulgarian'),
(65, 'Buriat'),
(66, 'Myanmar'),
(67, 'Caddo'),
(68, 'Galibi'),
(69, 'Catalan'),
(70, 'Valencian'),
(71, 'Caucasian'),
(72, 'Cebuano'),
(73, 'Celtic'),
(74, 'Central American Indian'),
(75, 'Chagatai'),
(76, 'Chamic languages'),
(77, 'Chamorro'),
(78, 'Chechen'),
(79, 'Cherokee'),
(80, 'Cheyenne'),
(81, 'Chibcha'),
(82, 'Chinese'),
(83, 'Chinook Pidgin'),
(84, 'Chipewyan'),
(85, 'Choctaw'),
(86, 'Chuukese'),
(87, 'Chuvash'),
(88, 'Classical Nepal Bhasa'),
(89, 'Coptic'),
(90, 'Cornish'),
(91, 'Corsican'),
(92, 'Cree'),
(93, 'English Pidgins'),
(94, 'French Pidgins'),
(95, 'Portuguese Pidgins'),
(96, 'Crimean Turkish'),
(97, 'Croatian'),
(98, 'Cushitic'),
(99, 'Czech'),
(100, 'Dakota'),
(101, 'Adangme'),
(102, 'Danish'),
(103, 'Dargwa'),
(104, 'Dari, Zoroastrian'),
(105, 'Delaware'),
(106, 'Digo'),
(107, 'Dinka'),
(108, 'Dogri'),
(109, 'Dogrib'),
(110, 'Dravidian'),
(111, 'Duala'),
(112, 'Duruma'),
(113, 'Dutch'),
(114, 'Dzhidi'),
(115, 'Bhutani'),
(116, 'Edo'),
(117, 'Efik'),
(118, 'Ancient Egyptian'),
(119, 'Ekajuk'),
(120, 'Elamite'),
(121, 'British English'),
(122, 'South African English'),
(123, 'Erzya'),
(124, 'Esperanto'),
(125, 'Estonian'),
(126, 'Eton'),
(127, 'Éwé'),
(128, 'Ewondo'),
(129, 'Fang'),
(130, 'Fanti'),
(131, 'Faroese'),
(132, 'Fijian'),
(133, 'Filipino'),
(134, 'Finnish'),
(135, 'Finno-Ugrian'),
(136, 'Fon'),
(137, 'Franco-Provençal'),
(138, 'Canadian French'),
(139, 'French'),
(140, 'Eastern Frisian'),
(141, 'Northern Frisian'),
(142, 'Western Frisian'),
(143, 'Friulian'),
(144, 'Fulah'),
(145, 'Ga'),
(146, 'Scottish Gaelic'),
(147, 'Galician'),
(148, 'Luganda'),
(149, 'Gayo'),
(150, 'Gbaya'),
(151, 'Ge''ez'),
(152, 'Georgian'),
(153, 'German'),
(154, 'Germanic'),
(155, 'Kikuyu'),
(156, 'Gondi'),
(157, 'Gorontalo'),
(158, 'Gothic'),
(159, 'Grebo'),
(160, 'Greek'),
(161, 'Guarani'),
(162, 'Gujarati'),
(163, 'Gun'),
(164, 'Gwich''in'),
(165, 'Haida'),
(166, 'Haitian Creole'),
(167, 'Hausa'),
(168, 'Hawaiian'),
(169, 'Hebrew'),
(170, 'Herero'),
(171, 'Hiligaynon'),
(172, 'Himachali'),
(173, 'Hindi'),
(174, 'Hittite'),
(175, 'Hmong'),
(176, 'Hungarian'),
(177, 'Hupa'),
(178, 'Iban'),
(179, 'Icelandic'),
(180, 'Ido'),
(181, 'Igbo'),
(182, 'Ijo languages'),
(183, 'Iloko'),
(184, 'Indic'),
(185, 'Indo-European'),
(186, 'Indonesian'),
(187, 'Ingush'),
(188, 'Interlingua'),
(189, 'Occidental Interlingue'),
(190, 'Inuktitut'),
(191, 'Kalaallisut'),
(192, 'Inupiaq'),
(193, 'Iranian'),
(194, 'Irish'),
(195, 'Iroquoian'),
(196, 'Italian'),
(197, 'Japanese'),
(198, 'Javanese'),
(199, 'Kachin'),
(200, 'Judeo-Arabic'),
(201, 'Dyula'),
(202, 'Kabardian'),
(203, 'Kabyle'),
(204, 'Kalenjin'),
(205, 'Kalmyk-Oirat'),
(206, 'Kamba'),
(207, 'Camba'),
(208, 'Kannada'),
(209, 'Kanuri'),
(210, 'Karachay-Balkar'),
(211, 'Karakalpak'),
(212, 'Karelian'),
(213, 'Karen languages'),
(214, 'Kashmiri'),
(215, 'Kashubian'),
(216, 'Kawi'),
(217, 'Kazakh'),
(218, 'Khasi'),
(219, 'Cambodian'),
(220, 'Khoisan'),
(221, 'Khotanese'),
(222, 'Khowar'),
(223, 'Kyrgyz'),
(224, 'Gilbertese'),
(225, 'Klingon'),
(226, 'Komi'),
(227, 'Kongo'),
(228, 'Konkani'),
(229, 'Korean'),
(230, 'Kosraean'),
(231, 'Kpelle'),
(232, 'Kru languages'),
(233, 'Kumam'),
(234, 'Kumyk'),
(235, 'Kurdish'),
(236, 'Kurukh'),
(237, 'Kutenai'),
(238, 'Kuanyama'),
(239, 'Ladino'),
(240, 'Lahnda'),
(241, 'Lamba'),
(242, 'Land Dayak'),
(243, 'Lango'),
(244, 'Lao'),
(245, 'Latin'),
(246, 'Latvian'),
(247, 'Lezghian'),
(248, 'Limburgs Plat'),
(249, 'Lingala'),
(250, 'Lithuanian'),
(251, 'Lojban'),
(252, 'Lozi'),
(253, 'Luba-Lulua'),
(254, 'Luba-Katanga'),
(255, 'Luiseño'),
(256, 'Lunda'),
(257, 'Nilotic Kavirondo'),
(258, 'Luxembourgish'),
(259, 'Luluyia'),
(260, 'Maasai'),
(261, 'Macedonian'),
(262, 'Madi'),
(263, 'Madurese'),
(264, 'Magahi'),
(265, 'Maithili'),
(266, 'Makasar'),
(267, 'Malagasy'),
(268, 'Malay'),
(269, 'Malayalam'),
(270, 'Divehi'),
(271, 'Maltese'),
(272, 'Manchu'),
(273, 'Mandar'),
(274, 'Mandingo'),
(275, 'Malinka'),
(276, 'Manobo'),
(277, 'Manx Gaelic'),
(278, 'Maori'),
(279, 'Mapuche'),
(280, 'Marathi'),
(281, 'Mari'),
(282, 'Marshallese'),
(283, 'Marwari'),
(284, 'Lugisu'),
(285, 'Mayan languages'),
(286, 'Kimbundu'),
(287, 'Manipuri'),
(288, 'Mende'),
(289, 'Mi''kmaq'),
(290, 'Middle Irish'),
(291, 'Minangkabau'),
(292, 'Mirandese'),
(293, 'Lushai'),
(294, 'Mohawk'),
(295, 'Moksha'),
(296, 'Moldavian'),
(297, 'Mon-Khmer'),
(298, 'Mongo'),
(299, 'Mongolian'),
(300, 'Motu, Hiri'),
(301, 'Multiple languages'),
(302, 'Munda languages'),
(303, 'Creek'),
(304, 'Mískito'),
(305, 'Mossi'),
(306, 'N''Ko'),
(307, 'Nahuatl languages'),
(308, 'Neopolitan'),
(309, 'Nauruan'),
(310, 'Navaho'),
(311, 'Northern Ndebele'),
(312, 'Nrebele'),
(313, 'Ndonga'),
(314, 'Nepali'),
(315, 'Nepal Bhasa'),
(316, 'Nias'),
(317, 'Niger-Kordofanian'),
(318, 'Nilo-Saharan languages'),
(319, 'Niuean'),
(320, 'No linguistic content'),
(321, 'Nogai'),
(322, 'North American Indian'),
(323, 'Northern Pastaza Quichua'),
(324, 'Norwegian'),
(325, 'Bokmål'),
(326, 'Norwegian Nynorsk'),
(327, 'Nubian'),
(328, 'Nuer'),
(329, 'Nyamwezi'),
(330, 'Nyanja'),
(331, 'Nyankole'),
(332, 'Runyoro'),
(333, 'Nzima'),
(334, 'Occitan'),
(335, 'Ojibwa'),
(336, 'Akiek'),
(337, 'Olu''bo'),
(338, 'Oriya'),
(339, 'Oromo'),
(340, 'Osage'),
(341, 'Ossetian'),
(342, 'Otomian'),
(343, 'Pahlavi'),
(344, 'Palauan'),
(345, 'Pali'),
(346, 'Pampangan'),
(347, 'Pangasinan'),
(348, 'Punjabi'),
(349, 'Panjabi, Mirpur'),
(350, 'Papiamento'),
(351, 'Papuan'),
(352, 'Central Pashto'),
(353, 'Farsi'),
(354, 'Philippine'),
(355, 'Phoenician'),
(356, 'Nigerian Pidgin'),
(357, 'Piemontese'),
(358, 'Pohnpeian'),
(359, 'Polish'),
(360, 'Brazilian'),
(361, 'Portuguese'),
(362, 'Prakrit languages'),
(363, 'Provençal'),
(364, 'Pushto'),
(365, 'Quechua'),
(366, 'Rajasthani'),
(367, 'Rapa Nui'),
(368, 'Rarotongan'),
(369, 'Romance'),
(370, 'Romanian'),
(371, 'Aromanian'),
(372, 'Romansch'),
(373, 'Romany'),
(374, 'Kirundi'),
(375, 'Russian'),
(376, 'Kinyarwanda'),
(377, 'Skolt Saami'),
(378, 'South Saami'),
(379, 'Salishan'),
(380, 'Samaritan Aramaic'),
(381, 'Sami languages'),
(382, 'Sami, Lule'),
(383, 'Sami, Northern'),
(384, 'Sami, Southern'),
(385, 'Samoan'),
(386, 'Sandawe'),
(387, 'Sango'),
(388, 'Sanskrit'),
(389, 'Santali'),
(390, 'Sardinian'),
(391, 'Sasak'),
(392, 'Swiss German'),
(393, 'Scots'),
(394, 'Selkup'),
(395, 'Semitic'),
(396, 'Serbian'),
(397, 'Serer'),
(398, 'Shan'),
(399, 'Shavian English'),
(400, 'Shona'),
(401, 'Shuar'),
(402, 'Sicilian'),
(403, 'Sidamo'),
(404, 'Sign Languages'),
(405, 'Sindhi'),
(406, 'Sinhalese'),
(407, 'Sino-Tibetan'),
(408, 'Siouan languages'),
(409, 'Slavic'),
(410, 'Old Church Slavonic'),
(411, 'Slovak'),
(412, 'Slovenian'),
(413, 'Lusoga'),
(414, 'Sogdian'),
(415, 'Somali'),
(416, 'Songhai'),
(417, 'Soninke'),
(418, 'Sorbian'),
(419, 'Lower Sorbian'),
(420, 'Upper Sorbian'),
(421, 'Northern Sotho'),
(422, 'Southern Sotho'),
(423, 'South American Indian'),
(424, 'Spanish'),
(425, 'Sranan'),
(426, 'Sukuma'),
(427, 'Sumerian'),
(428, 'Sundanese'),
(429, 'Susu'),
(430, 'Swahili'),
(431, 'Swati'),
(432, 'Swedish'),
(433, 'Syriac'),
(434, 'Tagalog'),
(435, 'Tahitian'),
(436, 'Tai'),
(437, 'Taino'),
(438, 'Tajik'),
(439, 'Tamashek'),
(440, 'Tidikelt'),
(441, 'Tamil'),
(442, 'Tatar'),
(443, 'Telugu'),
(444, 'Terêna'),
(445, 'Teso'),
(446, 'Tetum'),
(447, 'Thai'),
(448, 'Timne'),
(449, 'Tibetan'),
(450, 'Tigre'),
(451, 'Tigrinya'),
(452, 'Tiv'),
(453, 'Tlingit'),
(454, 'Tok Pisin'),
(455, 'Tokelau'),
(456, 'Bitonga'),
(457, 'Chitonga'),
(458, 'Tongan'),
(459, 'Tsimshian'),
(460, 'Tsonga'),
(461, 'Tswana'),
(462, 'Tumbuka'),
(463, 'Tupi languages'),
(464, 'Tupinambá'),
(465, 'Turkish'),
(466, 'Turkmen'),
(467, 'Tuvaluan'),
(468, 'Tuva'),
(469, 'Twi'),
(470, 'Udmurt'),
(471, 'Ugaritic'),
(472, 'Ukrainian'),
(473, 'Umbundu'),
(474, 'Uncoded languages'),
(475, 'Undetermined'),
(476, 'Urdu'),
(477, 'Uighur'),
(478, 'Uzbek'),
(479, 'Vai'),
(480, 'Venda'),
(481, 'Vietnamese'),
(482, 'Votic'),
(483, 'Volapük'),
(484, 'Wakashan'),
(485, 'Walloon'),
(486, 'Waray-Waray'),
(487, 'Washo'),
(488, 'Welsh'),
(489, 'Wallamo'),
(490, 'Wolof'),
(491, 'Xhosa'),
(492, 'Yakut'),
(493, 'Yao'),
(494, 'Yapese'),
(495, 'Sichuan Yi'),
(496, 'Yiddish'),
(497, 'Yoruba'),
(498, 'Yupik'),
(499, 'Zande'),
(500, 'Zapotec'),
(501, 'Zaza'),
(502, 'Zenaga'),
(503, 'Chuang'),
(504, 'Zulu'),
(505, 'Zuni');

1 registered user and 41 guests thanked already.

Users who thanked for this post:

Ray

  • "Ray" is male

Posts: 1,592

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 50847 / 7318

  • Send private message

84

Saturday, April 27th 2013, 2:11am

Michael, I have a CSV text file providing all of the languages supported by dotSUB, plus the lang-codes they use to reference them. I uploaded it into the Dev Group section in GDocs.
Language Codes Master CSV


My apologies for not being so present within this development lately. I recently had an issue with the member portal development that pretty much forced me to shut out most of the rest of the universe and focus only on fixing that problem. Now, I need to 'catch up' with where things are here and get back with you on these remaining questions.

For this database table, please adjust 'shortname' to the industry standard 'langcode'.
I have questions about the specific use of resource names within the data structure (using YouTube, Facebook, etc for table headers), since everything is subject to change over time and we need the ability to add more/other social networking sites as they become viable. If adding more in the future is not a problem, then please disregard the above (but give strong consideration to how we might best reflect these links on the front end).

Please define the intended use of the following:
description
homepage
team_permissions
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

1 registered user and 44 guests thanked already.

Users who thanked for this post:

michaelycus

  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

85

Saturday, April 27th 2013, 3:36am

Thank you Ray!

About the columns...


description - I think we don't need that. I can just delete it.
homepage - maybe that name is not right. I think it should be called 'website'. Is it ok?
team_permissions -

define('TEAM_NOT_ACTIVE', -1); // Not active teams has value -1 and won't be listed on the system, being hide for a while.
define('TEAM_CANNOT_TRANSCRIBE', 0); // Non english team has value 0. They only can translated videos and can't add new ones (just in the future).
define('TEAM_CAN_TRANSCRIBE', 1); // English team has value 1. They are allowed to add new medias.

'langcode' is a good name.

Adding new columns to represent social medias is not a problem but maybe I can consider to create another table to handle that.

Thanks again sir... It was really helpful. :fc-wink:

1 registered user and 50 guests thanked already.

Users who thanked for this post:

Ray

  • "Ray" is male

Posts: 1,592

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 50847 / 7318

  • Send private message

86

Saturday, April 27th 2013, 4:42am

Rather than delete 'description', perhaps it can be renamed to something like 'notes' and used to denote important info about each team, such as if the team is in need active coordination help (perhaps they are looking for someone to handle their YouTube channel, for example), if there is a peripheral issue going on with their related ZM chapter, VP Team or some other language-specific resource that we could try to help clear up, etc.. This element should only be viewable by registered members of the PMS. I have a much better way to advertise any needs each of the teams may have within the portal. ;)

'homepage' would be a little better as 'website', but some teams have more than one that they view as a kind of 'home base' or anchor to their overall language community. Perhaps a text field that allows a list of multiple sites would work best here?

team_permissions -
define('TEAM_NOT_ACTIVE', -1); // Not active teams has value -1 and won't be listed on the system, being hide for a while.
define('TEAM_CANNOT_TRANSCRIBE', 0); // Non english team has value 0. They only can translated videos and can't add new ones (just in the future).
define('TEAM_CAN_TRANSCRIBE', 1); // English team has value 1. They are allowed to add new medias.

The term 'TEAM' is not really necessary if the table itself is specific to the teams. (I just prefer simple, but obvious, data structures lol)

I'm a bit concerned about the 'team_can_transcribe' description. This group can transcribe, but not 'add new media'. Adding media should be limited to administration and, if different, the English Dep't coordinator(s), to avoid people joining the English Team just to add junk to the system. I'm very keen on protecting the materials & system from spammers and people who have little understanding of the importance of all of the incredible work that everyone is doing here.

Adding new columns to represent social medias is not a problem but maybe I can consider to create another table to handle that.

I was thinking the same thing. I strongly suspect that we're going to 'arrive at' the same structure that we intensely developed a couple of years back. :D
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

52 guests thanked already.
  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

87

Saturday, April 27th 2013, 2:28pm

I think we can handle the teams networking with that:

pms_social_networking(
team_id int,
type int,
address varchar(255)
)


When type can be constants:

SOCIAL_NETWORK_YOUTUBE = 1;
SOCIAL_NETWORK_FACEBOOK_GROUP = 2;
SOCIAL_NETWORK_FACEBOOK_PAGE = 3;
SOCIAL_NETWORK_TWITTER = 4;
SOCIAL_NETWORK_WEBSITE = 5;
SOCIAL_NETWORK_FORUM = 6;


(We can add more in the future if needed)

Finally, the language teams table can be reduced to:

pms_language_teams(
id int,
name varchar(45),
langcode varchar(45),
notes text,
team_permissions
)


About team_permissions: those are php constants and aren't table columns, that's why I call it TEAM_SOMETHING.

TEAM_NOT_ACTIVE = 0
TEAM_ACTIVE = 1;
TEAM_CAN_TRANSCRIBE = 2


- By default, all the teams will have value TEAM_NOT_ACTIVE... because its more easy to activate teams than desactive them. :)
- The only reason I use TEAM_CAN_TRANSCRIBE is because I need a way to differentiate the english team from the others and to have the option of 'Add video' in the top menu.

In the future I believe we need to have a option to 'Add a video non transcribed by LTI' because some teams want to translate other sources and don't want to wait for the english team. BUT those videos most to have a ABSOLUTELY CLEAR DISTINCTION from the other videos and those will be available only for that team.

1 registered user and 52 guests thanked already.

Users who thanked for this post:

Ray

  • "michaelycus" is male
  • "michaelycus" started this thread

Posts: 310

Date of registration: Jun 10th 2011

Language Team: Brazilian Team

Focus Group: Language Coordinator
LTI Development Group

Location: Lajeado - RS - Brazil

Thanks: 9573 / 13

  • Send private message

88

Sunday, June 16th 2013, 8:44pm

Hello everyone,

Sorry for take so long to reply. I'm working right now in the PMS + Portal integration.

Now our task is to connect the dots. The PMS needs to have the same levels of access used by Joomla, so we have to replace our old structure (that only had 4 levels) with what is used in Joomla.

Ray, I think you can help out with that. You know what those levels mean.



2 registered users and 38 guests thanked already.

Users who thanked for this post:

Ray, nomada

  • "Ray" is male

Posts: 1,592

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 50847 / 7318

  • Send private message

89

Sunday, June 16th 2013, 8:56pm

To some degree, we have to work in the opposite direction by adjusting the portal roles to how the PMS needs to view members. For example, the portal views all transcribers and translators equally as a single group, but if the PMS needs them separated, I will need to separate them in the portal system. That is only one example, of course, as I suspect that several combined roles may need to be expanded within the portal for this. I am about to go into a meeting, so I will hit you up in Skype after that to see if we can work out all of the adjustments that will be needed for this integration. :loveya:
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

1 registered user and 44 guests thanked already.

Users who thanked for this post:

nomada

© Linguistic Team International 2019
Context In Motion