On Wed, 27 Mar 2002, Ken Joy wrote:
> There are a couple of ways:
>
> a) you can use the search domain feature for all domains in a certain expiry
> range and export the search to CSV
>
> b) you can use the views under 'Renewal Management' (but, sadly, not export
> to CSV :(
>
These are all interactive processes, we need automation. That's why
we import the daily report.
I like the version number idea alot and that should be trivial to
implement. Then our end we store the current version number, if that
ever incremements we merely skip processing and log an exception
report.
Then we can go in and check the new format. No muss, no fuss.
-mark
> Check those out...see if one meets your needs?
>
> Thanks,
>
> Ken
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Mark Jeftovic
> > Sent: Wednesday, March 27, 2002 3:44 PM
> > To: Robert L Mathews
> > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: request API command for renewals
> >
> >
> >
> > You're right Robert, thats what we need. A method to get the complete
> > list of domains in each category.
> >
> > Right now the only way that I know of is to get it from the daily
> > list that goes out, which we slurp in and process. But when the
> > format changes, things go awry.
> >
> > Is there even any way in the RWI for this? We use it so seldomly that
> > I miss all kinds of things in there...
> >
> > -mark
> >
> > On Wed, 27 Mar 2002, Robert L Mathews wrote:
> >
> > > At 3/27/02 8:48 AM, Scott Allan wrote:
> > >
> > > >At 11:25 AM 3/27/02 -0500, Mark Jeftovic wrote:
> > > >
> > > >>I would like to see a command available in the API to obtain a list
> > > >>of renewals in specific categories, similar to what CIRA has in place.
> > > >>
> > > >>Every time OpenSRS changes the format of the daily renewal reminder
> > > >>(without notice) our parsers break resulting in unintended behaviour
> > > >>(most recently, prematurely deleting all domains in the deactivated
> > > >>category)
> > > >>
> > > >>If we have an API command to get the same results we can initiate
> > > >>specific jobs to get specific sets and eliminate the guesswork.
> > > >
> > > >
> > > >This already exists in get_domain - see page 60 of the API doc
> > > >at http://www.opensrs.org/docs/opensrs_client_protocol_spec252.PDF .
> > >
> > > I think Mark was saying he wanted to be able to get a list of all
> > > expiring domains for the reseller, not just a list of all domains
> > > expiring under a certain user profile. The current get_domain method
> > > requires that the reseller knows the username and password, and must be
> > > repeated for each profile.
> > >
> > > The current API is really geared towards end-user management functions
> > > (because you have to have the end-user password to even log in). To
> > > perform reseller-management functions, you have to use the RWI.
> > >
> > > What I'd like to see OpenSRS think about is creating a new set of API
> > > functions that perform the same types of tasks available in the RWI. For
> > > example, I'd like to be able to get the expiration dates for all my
> > > domains, set the locking for certain domains, etc. -- all the stuff
> > > people currently are told to do by scripting the RWI. Most of
> > the backend
> > > code for such an API already must exist inside the RWI CGIs
> > (and the CGIs
> > > could eventually be made to just call the API, which would probably help
> > > OpenSRS in the long run by making things use a documented interface).
> > >
> > > --
> > > Robert L Mathews, Tiger Technologies
> > >
> > > "The trouble with doing something right the first time is that nobody
> > > appreciates how difficult it was."
> > >
> >
> > --
> > mark jeftovic
> > http://www.easydns.com
> > http://mark.jeftovic.net
> >
> >
>
--
mark jeftovic
http://www.easydns.com
http://mark.jeftovic.net
