>-------- Оригинално писмо -------- >От: [email protected] >Относно: Matterhorn-users Digest, Vol 24, Issue 20 >До: [email protected] >Изпратено на: Сряда, 2012, Юли 18 11:39:47 EEST > > >Send Matterhorn-users mailing list submissions to > [email protected] > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >or, via email, send a message with subject or body 'help' to > [email protected] > >You can reach the person managing the list at > [email protected] > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Matterhorn-users digest..." > > >Today's Topics: > > 1. Re: Installing the core (Greg Logan) > 2. Re: How to add a capture agent to Matterhorn core server. > (Layman problem) (Solomon Melchizedek) > 3. Re: [Opencast Matterhorn] Please vote on user stories > (feature requests) by July 15th (Judy Stern) > 4. Re: Edit recording metadata (??????) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 17 Jul 2012 13:30:08 -0600 >From: Greg Logan >To: [email protected] >Subject: Re: [Matterhorn-users] Installing the core >Message-ID: >Content-Type: text/plain; charset="iso-8859-1" > >On 12-07-17 01:01 PM, Rub?n P?rez wrote: >> Hello, >> >> Try increasing the values in -XX:PermSize and -XX:MaxPermSize reasonably >> (according to the total memory in your machine). You can also make those >> two values equal (that way, java will try to reserve all the possible >> memory it will need at the beginning, and if there's not enough memory, it >> will fail right after you run the command). I'm assuming, of course, that >> you have plenty of memory in your system (2-4GB). >> >> For instance: export MAVEN_OPTS='-Xms256m -Xmx960m -XX:PermSize=512m >> -XX:MaxPermSize=512m' > >The official recommendation is -Xms1024m -Xmx1024m -XX:MaxPermSize=256m, >for the record :) > >G >> >> Best regards >> Rub?n >> >> 2012/7/17 adeseye a. (aa5g11) >> >>> Hello, >>> >>> while installing the core and executing the step: export >>> MAVEN_OPTS='-Xms256m >>> -Xmx960m -XX:PermSize=64m -XX:MaxPermSize=256m' >>> cd /opt/matterhorn/matterhorn_1.3.1 >>> mvn clean install -DdeployTo=/opt/matterhorn/felix/matterhorn >>> >>> I get this error: >>> >>> The system is out of resources. >>> Consult the following stack trace for details. >>> java.lang.OutOfMemoryError: PermGen space >>> >>> >>> Please how do I resolve this ? >>> >>> >>> Yemi >>> >>> >>> _______________________________________________ >>> Matterhorn-users mailing list >>> [email protected] >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>> >>> >> >> >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> > > > >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: signature.asc >Type: application/pgp-signature >Size: 836 bytes >Desc: OpenPGP digital signature >URL: > >------------------------------ > >Message: 2 >Date: Tue, 17 Jul 2012 14:37:11 -0700 >From: Solomon Melchizedek >To: [email protected] >Subject: Re: [Matterhorn-users] How to add a capture agent to > Matterhorn core server. (Layman problem) >Message-ID: > >Content-Type: text/plain; charset="iso-8859-1" > >Hello Greg, > I have some problem of 1.3.1. > > 1. Do I need to remove 1.2 before install 1.3.1. And how to >remove 1.2. > > 2. Which version of felix could matterhorn use? Felix 3.2.2 or >something else? > >Thanks > > > >On Thu, Jul 12, 2012 at 4:09 PM, Greg Logan [via Opencast] < >[email protected]> wrote: > >> On 12-07-12 04:53 PM, Solomon Melchizedek wrote: >> >> Hello Greg, >> >> >> >> That means I need to install matterhorn core and CA of version >> >> 1.3.1 or just install the 3rd >> >> party scripts of version 1.3.1 in my matterhorn of version 1.2? >> >> You would need to switch the entire Matterhorn codebase to 1.3.1. >> Installing the 3rd party tools with 1.3.1 and then trying to use the 1.2 >> code probably won't work. >> >> G >> >> >> >> >> Thanks >> >> >> >> >> >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >Message: 3 >Date: Tue, 17 Jul 2012 15:41:33 -0700 >From: Judy Stern >To: Opencast Matterhorn >Cc: Matterhorn Users >Subject: Re: [Matterhorn-users] [Opencast Matterhorn] Please vote on > user stories (feature requests) by July 15th >Message-ID: >Content-Type: text/plain; charset="us-ascii" > >I've gone ahead and resolved as "Won't Fix" 78 stories that had no >votes and no recent (2012) activity. Any can be individually reopened if you >feel that they shouldn't have been closed. > >I appreciate the work of all of you who contributed to the voting and >commenting and closing tickets known to be done. We're down to 154 open >stories. Still a lot, but definitely better. > >Thanks especially to those who entered the duplicate ticket number when they >found a duplicate; I closed these. I did notice a number of tickets had >comments to the effect that they were duplicates but didn't provide the >duplicate ticket number. It would be so incredibly helpful if the duplicate >ticket number was indicated: I don't think we should close a ticket as a >duplicate unless there's a link to the duplicate, so I'm leaving these open >for now. Many of them had votes. (Thus, a follow-up cleanup task, which I'm >not taking on myself now, is to go thru and resolve open tickets that have >duplicates, once those duplicates are found.) > >For those interested in the voting, here's the list of stories that do have >votes, sorted so you can see where the most "demand" is: >http://opencast.jira.com/secure/IssueNavigator.jspa?mode=hide&requestId=11269 > (I am proud to announce that MH-7088 To work effectivly a team must have >coffee. was in the top 3, tied with MH-8912 LDAP/Shibboleth authentication.) > >Judy > > > >On Jun 25, 2012, at 12:19 PM, Judy Stern wrote: > >> In a continued effort to cleanup Jira, let's focus on user stories. (User >> stories are the way we keep track of feature requests.) We have 250 open >> story cards, many of which are surely irrelevant at this point, so it's >> time to do a mass cleanout. Jira has a voting mechanism, and this seems >> like a fairly simple (if imperfect) way to get a sense of which stories are >> still relevant. >> >> Therefore, I request that anybody that is using or intends to use >> Matterhorn review the list of open stories and, by July 15th, add a vote >> to any that are important to your institution. Adding a vote is a simple >> matter of selecting "Add Vote" (either from the gear menu in the >> Issue Navigator or from the More Actions menu in the ticket itself). You'll >> need to have an account on the Matterhorn jira to vote, but not to review >> the open stories. (If you want to vote and don't already have an account, >> please visit >> https://opencast.jira.com/login.jsp?os_destination=%2Fsecure%2FDashboard.jspa >> and sign up.) >> >> After July 15th, I will resolve as Won't Fix each open story card UNLESS it >> gets at least one vote OR is currently active (which I'm defining as having >> been updated in 2012, or having a fix version of 1.5 or later). >> >> Please note that there's no absolute guarantee that stories that get lots >> of votes will get attention from developers; it *will* help, however, to >> highlight to developers what's important to the community and may increase >> the chances that such in-demand features will be addressed. And, if you >> care about something, voting is the best way to "keep it alive". >> >> You get extra points (well, you get extra appreciation) if you close a >> story because you recognize that it has already been done, or that it's a >> duplicate. (Please comment informatively). And, as always, the best thing >> you can do is to decide that you will contribute the work to address one of >> these tickets! >> >> Many thanks in advance for your participation in this activity, >> Judy Stern >> Educational Technology Services >> UC Berkeley >> _______________________________________________ >> Matterhorn mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn >> >> >> To unsubscribe please email >> [email protected] >> _______________________________________________ > >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >Message: 4 >Date: Wed, 18 Jul 2012 16:39:46 +0800 >From: ?????? >To: Matterhorn Users >Subject: Re: [Matterhorn-users] Edit recording metadata >Message-ID: > >Content-Type: text/plain; charset="utf-8" > >No, no, changing the title during the trim-hold-state worked with no >problem. But recordings with status "Finished" I can not find a way >to >change the title. > >2012/7/17 Ruediger Rolf > >> Changing this in the database will not help. The data comes from a SOLR >> search index. >> >> So changing the title in the hold-state did not work too? >> >> R?diger >> >> >> >> >> "??????" schrieb: >> >>> Hi R?diger, >>> >>> unfortunately I didn't succeed trying to edit the metadata of the >>> recording. I changed the episode.xml 'title' tag and nothing happened. >>> Should I change something in the DB? >>> >>> And thanks for the instructions to change the default workflow, it worked >>> perfect, no problem. >>> >>> Regards, >>> >>> Fernando. >>> >>> 2012/7/13 ?????? >>> >>>> Thank you R?diger. I will try all you have told me. >>>> >>>> Regards, >>>> >>>> Fernando. >>>> >>>> 2012/7/12 Ruediger Rolf >>>> >>>>> Hi Fernando, >>>>> >>>>> If you want to edit the title you will probably have to replace the >>>>> episode.xml. I'm not 100% sure as I did not try to do this with the rest >>>>> endpoints yet and I have no idea how any title information in the >>>>> workflow >>>>> is used. >>>>> >>>>> So I guess the default trim state is the better way for you to go and >>>>> it is the same way like we do it here. The default (full) workflow has a >>>>> mandatory trim in our installation. >>>>> >>>>> The first thing is that you have to decide which workflow will be the >>>>> default workflow. >>>>> One way to set the default workflow is to change this in the >>>>> config.properties: >>>>> org.opencastproject.workflow.default.definition=myworkflow >>>>> The other is to rename the workflows that your own workflow has the ID >>>>> "full" and you rename the original full workflow to something >>>>> else or >>>>> delete it. But make sure that you don't have two workflows with the same >>>>> ID. >>>>> I selected the second approach, as some tools use "full" by >>>>> default. >>>>> >>>>> The you have to do changes to your workflow: >>>>> Find every "${trimHold}" and replace it by >>>>> "true" in your workflow XML. >>>>> And it is probably the best to remove the trim-hold part from the >>>>> configuration panel section of the XML >>>>> >>>>> Good luck >>>>> R?diger >>>>> >>>>> Am 12.07.2012 04:40, schrieb ??????: >>>>> >>>>> And another detail, how can I add the trim/edit option to an unschedule >>>>> recording (set it up as default option if it is possible)? so when it is >>>>> ingested in the core server I will have the option to edit the metadata >>>>> before it is published. >>>>> >>>>> Thank you again. >>>>> >>>>> Fernando. >>>>> >>>>> 2012/7/12 ?????? >>>>> >>>>>> Hi R?diger, >>>>>> >>>>>> I still face the same issue. I use the workflow ID to get the xml of >>>>>> the package I want to edit its title, then I get a big xml piece of code >>>>>> (using GET /instance/{id}.xml method). I try to copy the xml code in >>>>>> the field of the "Updates a workflow instance" method, I >>>>>> change the >>>>>> tag and finally click on SUBMIT button. Response seems to be ok: >>>>>> >>>>>> Status: 204 (No Content) >>>>>> >>>>>> >>>>>> , but when I check the recording list or the media gallery the title >>>>>> of the recording is the same Unschedule-... >>>>>> >>>>>> Am I doing anything wrong? Thank you. >>>>>> >>>>>> Fernando. >>>>>> >>>>>> 2012/7/11 Ruediger Rolf >>>>>> >>>>>>> Hi Leslaw, >>>>>>> >>>>>>> you are right in the way that we recommend UUIDs as mediapackage IDs >>>>>>> (foldernames are these IDs). But unfortunately our own CA does not >>>>>>> respect >>>>>>> this convention when it comes to unscheduled recordings. >>>>>>> >>>>>>> R?diger >>>>>>> >>>>>>> Am 11.07.2012 11:49, schrieb Dr Leslaw Zieleznik: >>>>>>> >>>>>>> I think the folder name is wrong, it should be something like this: >>>>>>> >>>>>>> 743ccb86-a1b2-4894-a62e-54d17c2c04ea >>>>>>> >>>>>>> I am using such names ID when I am removing mediapackage via the >>>>>>> REST command >>>>>>> >>>>>>> Leslaw >>>>>>> >>>>>>> On Jul 11, 2012, at 10:42 AM, ?????? wrote: >>>>>>> >>>>>>> Thanks for the answer. >>>>>>> >>>>>>> But I still have the same problem. I use the folder name, in this >>>>>>> case: Unscheduled-captureagent-1347785909948, and if I try to use the >>>>>>> REST >>>>>>> service for workflow, read method, GET /instance/{id}.xml >>>>>>> I paste the folder name I I get a 404 error (but the folder is >>>>>>> there). >>>>>>> So I can not find a way to use REST services for workflow without >>>>>>> getting errors. >>>>>>> >>>>>>> Fernando >>>>>>> 2012/7/11 Dr Leslaw Zieleznik >>>>>>> >>>>>>>> You should use the recordings folder name as the ID. >>>>>>>> >>>>>>>> And the easy way to get it for the REST command is to: place the >>>>>>>> mouse on the folder, then use Rename, CTRL C and then CTRL V on the >>>>>>>> REST >>>>>>>> command field. >>>>>>>> >>>>>>>> Leslaw >>>>>>>> >>>>>>>> >>>>>>>> On Jul 11, 2012, at 9:31 AM, ?????? wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> I need to edit some metadata of some already Finished recordings. I >>>>>>>> have tried to use workflow REST service, but when I try to get the >>>>>>>> instance >>>>>>>> of the recording using the mediapackage ID (format: >>>>>>>> Unscheduled-captagentuser-1121342202932) I get >>>>>>>> >>>>>>>> >>>>>>>> Status: 400 (Bad Request) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Or 404 if I try directly from the Core Server. I I try with >>>>>>>> different parameters to find the package I want to edit I get the same >>>>>>>> error. What am I doing bad? >>>>>>>> >>>>>>>> Thanks in advance and best regards, >>>>>>>> >>>>>>>> Fernando Hernandez. >>>>>>>> _______________________________________________ >>>>>>>> Matterhorn-users mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>>>>> >>>>>>>> >>>>>>>> 1 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Matterhorn-users mailing list >>>>>>>> [email protected] >>>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>>>>> >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Matterhorn-users mailing list >>>>>>> [email protected] >>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>>>> >>>>>>> >>>>>>> ========== >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Matterhorn-users mailing >>>>>>> [email protected]http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> ________________________________________________ >>>>>>> R?diger Rolf, M.A. >>>>>>> Universit?t Osnabr?ck - Zentrum virtUOS >>>>>>> Heger-Tor-Wall 12, 49069 Osnabr?ck >>>>>>> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511 >>>>>>> E-Mail: [email protected] >>>>>>> Internet: www.virtuos.uni-osnabrueck.de >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Matterhorn-users mailing list >>>>>>> [email protected] >>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Matterhorn-users mailing >>>>> [email protected]http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> ________________________________________________ >>>>> R?diger Rolf, M.A. >>>>> Universit?t Osnabr?ck - Zentrum virtUOS >>>>> Heger-Tor-Wall 12, 49069 Osnabr?ck >>>>> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511 >>>>> E-Mail: [email protected] >>>>> Internet: www.virtuos.uni-osnabrueck.de >>>>> >>>>> >>>>> _______________________________________________ >>>>> Matterhorn-users mailing list >>>>> [email protected] >>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>>> >>>>> >>>> >>> ------------------------------ >>> >>> Matterhorn-users mailing list >>> [email protected] >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>> >>> >> -- >> Diese Nachricht wurde von meinem Mobiltelefon mit Kaiten Mail gesendet. >> >> _______________________________________________ >> Matterhorn-users mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> >> >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: > >------------------------------ > >_______________________________________________ >Matterhorn-users mailing list >[email protected] >http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > >End of Matterhorn-users Digest, Vol 24, Issue 20 >************************************************ > _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
