Difference between revisions of "Normalizing in a windows environment"
| Line 1: | Line 1: | ||
[[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Normalizing in a windows environment | [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > Normalizing in a windows environment | ||
| + | |||
| + | <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> | ||
This has not yet been implemented, and there are a number of ways to consider implementation. | This has not yet been implemented, and there are a number of ways to consider implementation. | ||
Latest revision as of 17:00, 11 February 2020
Main Page > Development > Development documentation > Normalizing in a windows environment
This has not yet been implemented, and there are a number of ways to consider implementation.
The first and simplest, would be running an MCP client on the server, and having a task for normalizing on a windows machine. This would be a different task than that sent to a linux machine.
The second would be enhancing the MCP to generate the normalization commands and distribute them. This carries with it a high level of complexity. It would be beneficial to modularize the way Jobs and Tasks are created in the MCP, and how they are determined to be successful or not.
The third way would be to have the Transcoder interact with the windows machine, and have the Transcoder order the windows machine to perform the appropriate operation.