You are not logged in.

[Testing] LTI System Manager

  • "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: 9592 / 13

  • Send private message

31

Sunday, March 17th 2013, 6:07pm

Ray... yes, I can create a new field named 'subtype'.

OK... Thank you folks!

1 registered user and 54 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: 9592 / 13

  • Send private message

32

Sunday, March 17th 2013, 7:05pm

Ray,

I believe you said we should have a field 'originator_id' and other field 'producer_id' in the table 'medias'. The producer is the person or entity that created the media (video, text, etc), but I'm not sure how it is different from the originator.

Maybe the tables should be something like this:

producers(
id int,
name varchar,
description varchar
)



originators(
id int,
name varchar,
description varchar
)

What the difference between producer and originator? What more information (fields) do we need?

1 registered user and 47 guests thanked already.

Users who thanked for this post:

Ray

  • "Ray" is male

Posts: 1,605

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 51131 / 7350

  • Send private message

33

Sunday, March 17th 2013, 8:33pm

In many cases, the two would be the same (e.g. TVP releases a new video short of Jacque discussing a specific topic and both would point back to TVP as producer and originator).

But we also handle numerous materials that originated from, for example, TZM (releasing a large video lecture by Peter), but then someone creates a new, much smaller video summary of that lecture. In this case, the originator would be TZM, but the producer (the person who put the video together) might be me or you. We need to be able to keep track of both in order to properly handle search requests (for an "Advanced Search" functionality to be added to future versions).
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

48 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: 9592 / 13

  • Send private message

34

Sunday, March 17th 2013, 8:48pm

Ok... do you remember that we have some constants to define the category of the media?
0 => "TZM",
1 => "PJ",
2 => "TVP",
3 => "COMM",
4 => "EXT"

So, are originator and producer fields from the same table? I mean, can they share the same table?
It's important to notice that you have to register a new producer/originator before create a new media if they weren't registered yet.

51 guests thanked already.
  • "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: 30509 / 980

  • Send private message

35

Sunday, March 17th 2013, 9:24pm

Of course, we are free to call them whatever we choose for the 'front end' displays (COMM could be called "Community Creations" or "Stuff made by awesome RBE lunatics!", for example).


Ah, Holy Clarification, Batman! :fc-batman:
Thanks,
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.

51 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: 9592 / 13

  • Send private message

36

Sunday, March 17th 2013, 10:07pm

That's the media table I talked about:


CREATE TABLE `medias` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`title` varchar(255) NOT NULL,
`description` varchar(512) NOT NULL,
`originator_id` int(11) DEFAULT NULL,
`producer_id` int(11) DEFAULT NULL,
`original_language_id` int(11) NOT NULL,
`current_language_id` int(11) NOT NULL,
`state` int(11) NOT NULL,
`type` int(11) NOT NULL,
`subtype` int(11) DEFAULT NULL,
`category` int(11) NOT NULL,
`parent_id` int(11) NOT NULL,
`working_location` varchar(255) DEFAULT NULL,
`original_location` varchar(255) DEFAULT NULL,
`publish_location` varchar(255) DEFAULT NULL,
`duration` time DEFAULT NULL,
`number_of_words` int(11) DEFAULT NULL,
`date_added` date DEFAULT NULL,
`date_finished` date DEFAULT NULL,
`forum_thread` varchar(255) DEFAULT NULL,
`comments` varchar(1024) DEFAULT NULL,
`notes` varchar(255) DEFAULT NULL,
PRIMARY KEY (`id`)
)

Ray, tell me if you see that we are missing something.

1 registered user and 48 guests thanked already.

Users who thanked for this post:

Ray

  • "Ray" is male

Posts: 1,605

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 51131 / 7350

  • Send private message

37

Monday, March 18th 2013, 2:24am

The originator & producer identifications will, for most items, be entities rather than people (i.e. TZM, TVP, Metanoia Films, etc.), so perhaps they could be set up as text fields, rather than tying them to internal registered IDs.

`originator` varchar(255) DEFAULT NULL,
`producer` varchar(255) DEFAULT NULL,

However, that may work negatively against consistency for advanced Search results later.
If we use IDs, will it be simple enough to add new ones to those lists?



Other thoughts:

`current_language_id` int(11) NOT NULL,
// If we are going to use long labels, this one might be better served as `project_language_id` int(11) NOT NULL, , since it will always refer to the project being worked on, just within individual languages.


`working_location` varchar(255) DEFAULT NULL,
`original_location` varchar(255) DEFAULT NULL,
`publish_location` varchar(255) DEFAULT NULL,
// We still need space for recording two Repository locations, especially for handling ToDo functionality (but also for everyone's reference). The member portal will provide the second location (to be moved later to the public portal) for storing all completed works (not just SRTs, but also PDFs, documents, etc.), giving us two Repository locations of equal importance to record and share from here (one for embedding or linking to the source, and the other one for public downloading from the portal to create custom DVDs, etc.).


`comments` varchar(1024) DEFAULT NULL,
`notes` varchar(255) DEFAULT NULL,
// I'm thinking the terms may be reversed here.
Comments are generally short and only added by an admin to provide any additional info needed by teams or public viewers.
Notes are currently handled with online pads so that each stage of tasks can leave more extensive reference information for all future stages (a progression of information provided, and added to, by the transcribers, proofreaders, time-shifters, translators, etc.)

That's all I can see right now, but this is always subject to change. :giggle:
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

52 guests thanked already.
  • "Ray" is male

Posts: 1,605

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 51131 / 7350

  • Send private message

38

Monday, March 18th 2013, 9:59am

Ah, I just remembered a VERY important one that is not represented there yet. Priority!
We need a very visible way of showing where the material falls in terms of priority to the overall understanding of the global RBE concept, usually provided to us by the original sources (TVP, TZM, etc.)

The original span I used for the wiki's representation of this was "Top", "High" & "Other", but this should likely be expanded a bit to accommodate the wider variety of items now included in the system.
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

50 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: 9592 / 13

  • Send private message

39

Monday, March 18th 2013, 12:03pm

However, that may work negatively against consistency for advanced Search results later.
If we use IDs, will it be simple enough to add new ones to those lists?

Well... I think its not a good idea to create a database of originator/producer since it can become hard to maintain. So a simple textfield will be enough, like they do in dotsub: http://dotsub.com/mediaupload

Other thoughts:

`current_language_id` int(11) NOT NULL,
// If we are going to use long labels, this one might be better served as `project_language_id` int(11) NOT NULL, , since it will always refer to the project being worked on, just within individual languages.

Ok... done!

`working_location` varchar(255) DEFAULT NULL,
`original_location` varchar(255) DEFAULT NULL,
`publish_location` varchar(255) DEFAULT NULL,
// We still need space for recording two Repository locations, especially for handling ToDo functionality (but also for everyone's reference). The member portal will provide the second location (to be moved later to the public portal) for storing all completed works (not just SRTs, but also PDFs, documents, etc.), giving us two Repository locations of equal importance to record and share from here (one for embedding or linking to the source, and the other one for public downloading from the portal to create custom DVDs, etc.).

Ok... can you name those field?

`comments` varchar(1024) DEFAULT NULL,
`notes` varchar(255) DEFAULT NULL,
// I'm thinking the terms may be reversed here.
Comments are generally short and only added by an admin to provide any additional info needed by teams or public viewers.
Notes are currently handled with online pads so that each stage of tasks can leave more extensive reference information for all future stages (a progression of information provided, and added to, by the transcribers, proofreaders, time-shifters, translators, etc.)

That's all I can see right now, but this is always subject to change. :giggle:
I thought we can use 'comments' in a textarea and write some things that are important for the team.
And 'notes' are links to online pads. 255 chars are ok for links. What do you think?

Priority field added! What do you think in using 5 levels of priority? We can use stars :star:

2 registered users and 52 guests thanked already.

Users who thanked for this post:

nomada, Ray

  • "Ray" is male

Posts: 1,605

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 51131 / 7350

  • Send private message

40

Monday, March 18th 2013, 6:23pm

So a simple textfield will be enough, like they do in dotsub

Agreed. There is no way to predict how many producers or originators there may be in the future.

can you name those field?

The repository locations are already known, but nothing is ever 'forever'. We already know that the second location will definitely change once the public portal is launched.
So, I would suggest:

repo_storage_location (representing dotSUB's Repo location)
  • Typical data would be a link to dotSUB's location
  • http://dotsub.com/view/482f9113-c1a3-4af9-b039-e9e2deee6e43

repo_distribution_location (representing the portal's distribution location)


I thought we can use 'comments' in a textarea and write some things that are important for the team.
And 'notes' are links to online pads. 255 chars are ok for links. What do you think?

That makes perfect sense to me. :loveya:


Priority field added! What do you think in using 5 levels of priority? We can use stars

Colors are much more noticeable than stars, but perhaps they can be combined.


A Top Priority item would need to be displayed in deep red to immediately draw attention to that aspect (not only in its own description page, but also when included in a table listing or as a search result)
High priority could be more of an orange
Medium as yellow
etc.
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

51 guests thanked already.
  • "MarlysePi" is female

Posts: 139

Date of registration: Oct 26th 2011

Language Team: English, French

Focus Group: English Transcriber
English Proofreader
Translator
Translation Proofreader
Final Reviewer

Location: Morges, Switzerland

Thanks: 5810 / 52

  • Send private message

41

Tuesday, March 19th 2013, 5:26pm

Testing

Hi developers! You are doing an amazing job!
I want to offer my services as a tester once you have something visible and usable by non-coders.
My point of view as a lambda user could be useful, to avoid too much complexity.
Do you have a sitemap yet ?
I don't know if you already have people doing this for you, but anyway I thought I would mention it.
Don't hesitate to contact me if you need to test something "from outside".
Cheers :smiley:
Marlyse

4 registered users and 50 guests thanked already.

Users who thanked for this post:

Ray, nomada, michaelycus, Borislav/lizardman

  • "MarlysePi" is female

Posts: 139

Date of registration: Oct 26th 2011

Language Team: English, French

Focus Group: English Transcriber
English Proofreader
Translator
Translation Proofreader
Final Reviewer

Location: Morges, Switzerland

Thanks: 5810 / 52

  • Send private message

42

Wednesday, March 20th 2013, 2:59pm

Status of videos

Here are a few suggestions:


This would be for the English team "page"
- Proposed by (anyone can propose a video for translation): Ready for approval
- New (once it is accepted) : Open for transcription
- Transcription in progress (is it possible technically to name the person doing it ? if not, ignore all the "by whom")
- Transcription complete: Ready for proofreading
- Proofreading round (or R)1 in progress (by whom)
- Proofreading R1 complete - Ready for proofreading round 2

- Proofreading R2 in progress (by whom)
- Proofreading R2 complete: Ready for final review (or FR)
- Final review complete (by whom): Open for translation
- Under review and repair (following error reporting for example)


Be aware that from this status onward, it branches out into all the different languages.
Therefore the rest of the statuses will need to be replicated on each different language "pages" (or whatever they will be called on this site)

Example for French language

- Translation in progress (by whom)
- Translation complete: Ready for proofreading
- Proofreading R1 in progress (by whom)
- Proofreading R1 complete: ready for Proofreading R2
- Proofreading R2 in progress (by whom)
- Proofreading R2 complete : ready for Final Review (or FR)
- Final Review complete (by whom): ready for publication
- Published in repository, locked
- Under review and repair (following error reporting)

For videos being translated from another language into English, the same statuses would apply as the ones on the English team "page".

1 registered user and 54 guests thanked already.

Users who thanked for this post:

Ray

  • "lizardman" is male

Posts: 578

Date of registration: Jun 3rd 2011

Language Team: Bulgarian

Focus Group: Translation Proofreader
LTI Administration Group

Location: Plovdiv, Bulgaria

Thanks: 25406 / 483

  • Send private message

43

Wednesday, March 20th 2013, 7:49pm

Hi Marlyse,

About the "Proposed by" stage, it might be quite counterproductive to have such stage. First, because it is a system for the materials that are actually being worked on. If there is no work being done on the material, there's no point in including it in the system, or at least that's my understanding of all of this.

Secondly, since everyone can propose a material for translation, if the proposals go directly to the system, we can get all sorts of stuff in there...

Otherwise, the statuses you suggest are pretty much what has been worked out for the Eng. team, as well as for the translation teams. :)

2 registered users and 52 guests thanked already.

Users who thanked for this post:

MarlysePi, michaelycus

  • "Ray" is male

Posts: 1,605

Date of registration: May 23rd 2011

Language Team: Global

Focus Group: LTI Administration Group

Location: Michigan, US

Thanks: 51131 / 7350

  • Send private message

44

Thursday, March 21st 2013, 12:50am

Agreed. Proposals will continue to be taken in the forum and will only be added to this system if/when they are added to THE system.

As for beta testing, the entire English Dep't is going to be our initial 'lab rat' for working out any buggies that get past the alpha phases. :fc-after-boom:
Signature from »Ray« Earth For Sale:
Slightly Used; inquire within

2 registered users and 50 guests thanked already.

Users who thanked for this post:

MarlysePi, michaelycus

  • "MarlysePi" is female

Posts: 139

Date of registration: Oct 26th 2011

Language Team: English, French

Focus Group: English Transcriber
English Proofreader
Translator
Translation Proofreader
Final Reviewer

Location: Morges, Switzerland

Thanks: 5810 / 52

  • Send private message

45

Thursday, March 21st 2013, 7:20am

Status of videos

Otherwise, the statuses you suggest are pretty much what has been worked out for the Eng. team, as well as for the translation teams.
I am not sure that the statuses I proposed are the same as what was done for the English Team. What I was proposing was a more detailed workflow, where each completed task leads automatically to the next stage, without any needed intervention from admins.
Is this what you guys are doing ?

46 guests thanked already.
© Linguistic Team International 2019
Context In Motion