Transcoder - Revision history

Sallain at 22:05, 11 February 2020

2020-02-11T22:05:07Z

Jhs: /* Development */

2013-05-15T22:42:59Z

Development

Jhs: /* Example */

2012-12-11T00:22:57Z

Example

Joseph: /* Create FileIds */

2012-08-21T23:20:12Z

Create FileIds

Joseph: /* Example */

2012-08-21T20:48:15Z

Example

Joseph: /* =Create processing link to execute */

2012-08-21T20:45:52Z

=Create processing link to execute

Joseph: /* Example */

2012-08-21T20:45:09Z

Example

Joseph: /* Example */

2012-08-21T20:42:49Z

Example

Joseph: /* Example */

2012-08-21T19:52:58Z

Example

Joseph: /* Example */

2012-08-21T19:40:04Z

Example

← Older revision		Revision as of 22:05, 11 February 2020
Line 1:		Line 1:
		+	<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">This page is no longer being maintained and may contain inaccurate information. Please see the [https://www.archivematica.org/docs/latest/ Archivematica documentation] for up-to-date information.</div><p>
		+
	Transcode: convert (language or information) from one form of coded representation to another.[ source: [http://oxforddictionaries.com/view/entry/m_en_gb0876960#m_en_gb0876960 Oxford English Dictionary] ]		Transcode: convert (language or information) from one form of coded representation to another.[ source: [http://oxforddictionaries.com/view/entry/m_en_gb0876960#m_en_gb0876960 Oxford English Dictionary] ]

← Older revision		Revision as of 22:42, 15 May 2013
Line 23:		Line 23:


−	Integration with the MCP was done by relating commands to Microservice chain links. The Transcoder links (~~MicroserviceDChainLinks~~ of this type) have a one to one relationship with the tasksConfigs, which have a one to one relationship with the CommandRelationships. The protocol between the client and server is based on the command Relationships's pk. The MCP assigns a task to the client to perform x commandRelationship on y file (identified by fileUUID). The client can pull the information required to execute the command from the database.	+	Integration with the MCP was done by relating commands to Microservice chain links. The Transcoder links (MicroserviceChainLinks of this type) have a one to one relationship with the tasksConfigs, which have a one to one relationship with the CommandRelationships. The protocol between the client and server is based on the command Relationships's pk. The MCP assigns a task to the client to perform x commandRelationship on y file (identified by fileUUID). The client can pull the information required to execute the command from the database.

	Why the change? To support all clients not having to support all normalization tools, the tasks needed to be assigned by tool availibility. Currently the archivematica-client package depends on all the tools required, but there are situations where this will be required. While these are not currently implemented an example would be normalizing on a windows machine, using microsoft office. The windows machine could theoretically run a client, but it wouldn't be able to support the standard archivematica tools, as they are linux based. To differentiate the two, use the supportedBy field in the Commands table.		Why the change? To support all clients not having to support all normalization tools, the tasks needed to be assigned by tool availibility. Currently the archivematica-client package depends on all the tools required, but there are situations where this will be required. While these are not currently implemented an example would be normalizing on a windows machine, using microsoft office. The windows machine could theoretically run a client, but it wouldn't be able to support the standard archivematica tools, as they are linux based. To differentiate the two, use the supportedBy field in the Commands table.

@@ Line 28: / Line 28: @@
 ==Example==
-Normalization commands are created as part of the archivematica install. They are kept in the database, and populated upon install by the [http://code.google.com/p/archivematica/source/browse/trunk/src/transcoder/share/mysql?r=3224 /usr/share/archivematica/transcoder/mysql] sql script.
+Normalization commands are created as part of the archivematica install. They are kept in the database, and populated upon install by the [https://github.com/artefactual/archivematica/blob/master/src/transcoder/share/mysql /usr/share/archivematica/transcoder/mysql] sql script.
 ===Create Commands===
 First, create the command(s) that will need to run. These commands can even be complete scripts. The command Type will need to be defined. A list of supported command types is in the CommandTypes table. You may also wish to create a special command for getting the event detail text for the event.

@@ Line 133: / Line 133: @@
 </div>
 ===Create FileIds===
-Second, create the file type. The FileIDs entry is a cover all, for future releases supporting more than one type of file identification. Every file identificaiton will have a unique corresponding entry in the FileIDs. The validPreservationFormat, and validAccessFormat relate to what appears in the normalization report. These are for identifying files at risk of format obsolescence, with failed or no normalization command. The FileIDsByExtension is the entry that links a '.mpg' file to the fileID.
+Second, create the file type. The FileIDs entry is a cover all, for future releases supporting more than one type of file identification. Every file identificaiton will have a unique corresponding entry in the FileIDs. The validPreservationFormat, and validAccessFormat relate to what appears in the normalization report. These are for identifying files at risk of format obsolescence, with failed or no normalization command. The FileIDsByExtension is the entry that links a '.mpg' file to the fileID. Files are related to their extension fileID's in the 'Identify Files ByExtension' micro-service, creating an entry in the FilesIdentifiedIDs table.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
 See code:

@@ Line 28: / Line 28: @@
 ==Example==
 ===Create Commands===
 First, create the command(s) that will need to run. These commands can even be complete scripts. The command Type will need to be defined. A list of supported command types is in the CommandTypes table. You may also wish to create a special command for getting the event detail text for the event.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:800px">

@@ Line 172: / Line 172: @@
 </div>
-====Create processing link to execute===
+===Create processing link to execute===
 Lastly, create the MicroServiceChainLink to be processed by the MCP, containing relationship between the link and the CommandRelationship.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
@@ Line 189: / Line 189: @@
 </div>
 To see all of the code as one.
 <div class="toccolours mw-collapsible mw-collapsed" style="width:800px">

← Older revision		Revision as of 19:40, 21 August 2012
Line 132:		Line 132:
	</div>		</div>
	</div>		</div>
		+
		+	Second create the file type. The FileIDs entry is a cover all, for future releases supporting more than one type of file identification. Every file identificaiton will have a unique corresponding entry in the FileIDs. The FileIDsByExtension is the entry that links a '.mpg' file to the fileID.
		+	<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
		+	See code:
		+	<div class="mw-collapsible-content"><pre>
		+	INSERT INTO FileIDs
		+	(description, validPreservationFormat, validAccessFormat)
		+	VALUES (
		+	'A .mpg file', FALSE, FALSE
		+	);
		+	set @fileID = LAST_INSERT_ID();
		+
		+	INSERT INTO FileIDsByExtension
		+	(Extension, FileIDs)
		+	VALUES (
		+	'mpg',
		+	@fileID
		+	);
		+	</pre>
		+	</div>
		+	</div>
		+