RAS user data for CitEc
Jose Manuel Barrueco writes
btw, I'm going to implement Christian suggestions to allow the input of references in a web form. The first step would be the identification of the user with RAS data. You mentioned that it coud be possible to rsync the ras tables into sopri?
I don't think we want to do that. They are verry bulky. We could just rsync the users table, but I don't tihnk this is a good idea either. I rather suggest we rsync the userdata folder, and you write a routine to update a table from that folder. BTW, this could be done quickly with using Ivan's update deamon. That way you could update it very quickly, if you want a special challenge. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
Thomas Krichel writes
Jose Manuel Barrueco writes
btw, I'm going to implement Christian suggestions to allow the input of references in a web form. The first step would be the identification of the user with RAS data. You mentioned that it coud be possible to rsync the ras tables into sopri?
I don't think we want to do that. They are verry bulky. We could just rsync the users table, but I don't tihnk this is a good idea either. I rather suggest we rsync the userdata folder, and you write a routine to update a table from that folder. BTW, this could be done quickly with using Ivan's update deamon. That way you could update it very quickly, if you want a special challenge.
Actually, the other thing that we could do is to give CitEc access to the RAS tables. This can be done using ssl. I think this is probably the quickest way to get it done, and the most responsive to users. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
On Wed, 22 Jun 2011, Thomas Krichel wrote:
Thomas Krichel writes
Jose Manuel Barrueco writes
btw, I'm going to implement Christian suggestions to allow the input of references in a web form. The first step would be the identification of the user with RAS data. You mentioned that it coud be possible to rsync the ras tables into sopri?
I don't think we want to do that. They are verry bulky. We could just rsync the users table, but I don't tihnk this is a good idea either. I rather suggest we rsync the userdata folder, and you write a routine to update a table from that folder. BTW, this could be done quickly with using Ivan's update deamon. That way you could update it very quickly, if you want a special challenge.
Actually, the other thing that we could do is to give CitEc access to the RAS tables. This can be done using ssl. I think this is probably the quickest way to get it done, and the most responsive to users.
Note that Dan will soon start to work on migrating RAS to St. Louis. Also, at some point we want to get an OpenID-like system for RAS that could be used by CitEc and others.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
_______________________________________________ RAS-run mailing list RAS-run@lists.openlib.org http://lists.openlib.org/cgi-bin/mailman/listinfo/ras-run
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
'Christian Zimmermann' writes
Note that Dan will soon start to work on migrating RAS to St. Louis.
Please give me a bit of notice before you shut nebka down. What will happen to the hardware?
Also, at some point we want to get an OpenID-like system for RAS that could be used by CitEc and others.
Yes. I already suggested this as a development point. But until then, I want something that work here and now. Do you agree with ssl mysql access? Will you be able to fund such development to be done by Ivan? Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
On Wed, 22 Jun 2011, Thomas Krichel wrote:
'Christian Zimmermann' writes
Note that Dan will soon start to work on migrating RAS to St. Louis.
Please give me a bit of notice before you shut nebka down.
No problem.
What will happen to the hardware?
Bob wants is back for parts.
Also, at some point we want to get an OpenID-like system for RAS that could be used by CitEc and others.
Yes. I already suggested this as a development point. But until then, I want something that work here and now. Do you agree with ssl mysql access?
Dan should be able to tell you whether this is OK here.
Will you be able to fund such development to be done by Ivan?
I am supposed to meet people here soon for this.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
-- Christian Zimmermann FIGUGEGL! Economic Research Federal Reserve Bank of St. Louis P.O. Box 442 St. Louis MO 63166-0442 USA http://ideas.repec.org/zimm/
'Christian Zimmermann' writes
Bob wants is back for parts.
Excellent idea! Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
Also, at some point we want to get an OpenID-like system for RAS
that could be used by CitEc and others.
Yes. I already suggested this as a development point. But until then, I want something that work here and now. Do you agree with ssl mysql access?
Dan should be able to tell you whether this is OK here.
This can't be a long-term solution, but we can do this until an OpenID-like system can be setup.
Dan Hayes writes
This can't be a long-term solution,
What is the problem with it?
but we can do this until an OpenID-like system can be setup.
I agree that we should be working towards this goal but progress may not be fast. Count months rather than weeks. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
The problem long-term is that our risk management team does not allow outside access to our servers. We can get a temporary exemption, but it would have to be temporary. However, we would have flexibility with how we define temporary, within reason. Months won't be a problem, a year likely won't be a problem, beyond that likely will. Is that time frame sufficient? On Thu, Jun 23, 2011 at 8:04 PM, Thomas Krichel <krichel@openlib.org> wrote:
Dan Hayes writes
This can't be a long-term solution,
What is the problem with it?
but we can do this until an OpenID-like system can be setup.
I agree that we should be working towards this goal but progress may not be fast. Count months rather than weeks.
Cheers,
Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
Dan Hayes writes
The problem long-term is that our risk management team does not allow outside access to our servers.
You mean, other than http...
We can get a temporary exemption, but it would have to be temporary. However, we would have flexibility with how we define temporary, within reason. Months won't be a problem, a year likely won't be a problem, beyond that likely will. Is that time frame sufficient?
I would hope it is. One thing that should help our case is that we only need access from one IP address. Cheers, Thomas Krichel http://openlib.org/home/krichel http://authorclaim.org/profile/pkr1 skype: thomaskrichel
participants (3)
-
'Christian Zimmermann' -
Dan Hayes -
Thomas Krichel