SayMore projects into RAMP & REAP

[Mari-Sisko Khadgi]

Hi,

 

Has anyone been using the RAMP feature in SayMore, in order to put materials into REAP?  What kind of experience have you had?

 

We were planning to do this, but soon realized that it is very cumbersome, as SayMore makes a separate RAMP package of each session.  We have 6 different projects and each of them have 70-100 sessions, so to do RAMP will take a really really long time.  For each RAMP package there are 20+ steps with several questions.

 

What we would like to do, is to make one single RAMP package for one project.  Can anyone think of a way to do this now?  Or is this something that we should suggest for next SayMore development round?

 

 

Regards,
Mari-Sisko

[John Hatton]

Hi Mari-Sisko,

I too would like to hear from anyone... I'm hoping that it's not too difficult to simply use RAMP directly.

> Or is this something that we should suggest for next SayMore development round?

This is a well-known top priority. However we don't have programmers to work on SayMore at this time. It never hurts to express your needs though, through whatever channels you have.

jh

--
You received this message because you are subscribed to the Google Groups "SayMore" group.
To unsubscribe from this group and stop receiving emails from it, send an email to saymore+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

John Hatton

Senior Software Engineer/Program Manager
Language Software Development
SIL International

[Ryan Pennington]

Hi Mari-Sisko,

This is the same reason I have not archived. I just can’t spend that kind of time. It’s certainly a dilemma!

Ryan

[thesarah]

I have done this and it is indeed time consuming. Sorry I cannot be more comforting. On the other hand it is something that you can do here-and-there when you, or someone you have trained, have 15 minutes or more to spare (perfect job for a student intern *evil grin*).

There is a SayMore development proposal that has been in the pipeline for awhile, presumably waiting for manpower as John said. I am 98% positive (I helped write it but haven't looked at it for awhile) that it will allow SayMore users to bypass RAMP altogether. And archive a SayMore project as a single corpus instead of archiving session by session.

Sarah Moeller

[John Hatton]

> it will allow SayMore users to bypass RAMP altogether. 

For a project that isn't getting done for lack of dev resources, adding "and reinvent RAMP" is probably not our best strategy :-)  I could probably find the original proposal, but, being lazy... do you recall why that was proposed? Maybe that's worth discussing here.

[Hugh Paterson III]

@John and others,

I am not sure that this is actually a SayMore issue. I mean certainly creative works are not being submitted to REAP because of large amounts of time consuming detailed work which is needed in each project. And SayMore has a role in lessening the work (mouse clicks) needed to achieve goals. However, I think that part of the issue is the architecture of REAP. For that reason I suggest that this conversation move to the Insite Wiki space for REAP. Everyone here who is concerned with submissions to REAP should already have access to that space. By having the conversation in the REAP wiki space we are able to leave a relevant record for the REAP architects to review as they consider REAP architecture issues.

All the best, 

Hugh Paterson III

[thesarah]

I have two pieces of good news related to this. 

First, I recently talked with Paul Nelson at SIL. He thinks that "one button" REAP archiving will be available next spring. It should deposit a whole project in one fell swoop AND create a "homepage" in REAP for the corpus. The "homepage" will display corpus-level metadata (from Project tab) and link to all deposited Sessions.

This is not "reinventing RAMP". At least not anymore than SayMore already did. A motivating issue behind the proposal was that the process from SM to REAP via RAMP required depositors to re-enter some metadata already existing in SayMore while transferring other metadata automatically to RAMP. The proposed changes was meant to correct that, and as we thought through it, we realized that it was just as easy to bypass RAMP since much of the other requested info is not applicable to language documentation corpora. 

Second, I was told by someone at U of Hawaii that there is a high-level proposal submitted in Australia, or USA (i.e. NSF), or both, to fund SM development that, from what I understand, would essentially allow SM users to deposit as easily into any major archive as SIL members should be able to do once the new developments are completed. I don't have a lot of details, but it is something I'm expecting to hear more about, and hopefully soon. 

[Mari-Sisko Khadgi]

This is wonderful news!  I’m also looking forward to hearing more good news about the Australia/US proposal.

 

Thanks so much for all of you who are working on making SayMore a better tool for all of us!

 

Regards,
Mari-Sisko

--