Hello All!

OK, will include all networks within all three files but that brings up a possible issue namely :=


ELIST.RPT listing produced in echo with network order - straight forward.

ELIST.NO Like wise as the network name is included in listing order by showing per line as deleted date, Network, Echo Tag, description.

But ELIST.NA does have an iisue as that currently lists as :-

Echo Tag, Description.

Now the problem is if any one uses an automated process that reads this file to
update their BBS or other software How ever if not, then I can add the NEtwork name at the beginning so the line/s will look like :=
Network, Echo Tag, Description.

Has any one a problem with this change and err, why ?

I must admit years back, ok many years back I did use this file as my master for new echo's to add to the bbs but stopped when its content was low compared to what is available.

So if no one uses it in the auto mode I can add an extra field name at the beginning.

Other wise there is no way of knowing what network a specific echo belongs to.

Comments welcome,

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hello Vincent Coen!

** On Monday 07.06.21 - 17:56, Vincent Coen wrote to All:

But ELIST.NA does have an iisue as that currently lists as :-

Echo Tag, Description.

Now the problem is if any one uses an automated process
that reads this..

[...]

Other wise there is no way of knowing what network a
specific echo belongs to.

Since ELIST.RPT contains ALL the other networks, and each
network is identified, why not produce corresponding
<network>.NA and <network>.NO files?


--
../|ug
--- OpenXP 5.0.50
* Origin: (2:221/1.58)

On 07 Jun 2021 at 05:04p, August Abolins pondered and said...

Since ELIST.RPT contains ALL the other networks, and each
network is identified, why not produce corresponding
<network>.NA and <network>.NO files?

this idea appeals to me... keeps it simple in that you just split out data by othernet and folks can pick and choose with ease what they want to dip into
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello All!

Wednesday June 09 2021 13:47, Paul Hayton wrote to August Abolins:

On 07 Jun 2021 at 05:04p, August Abolins pondered and said...

Since ELIST.RPT contains ALL the other networks, and each
network is identified, why not produce corresponding
<network>.NA and <network>.NO files?

this idea appeals to me... keeps it simple in that you just split out
data by othernet and folks can pick and choose with ease what they
want to dip into

So far the system has been changed to generate the ELIST.RPT file in network order
with the trailer block now showing for example :

--
{ 164 records reported }
{ in 2 networks }
[FIDO,FSXNET]

{ 6 records with Warnings reported }

--

This involved changing the database to have a primary key containing network, echo-tag so any reporting does come out in network order.

So all networks found are counted and listed (using ',' to separate and held in
[].

There is a maximum size limit for this of 80 characters which is more to keep it
on one line and see-able on a page.

At the moment I have NOT changed the ELIST.NA to include a new field (Network) at
the start of the line as I am still waiting for comments regarding this one - mostly to see if any one uses this file as input to any automated software that
would get upset by such a change. To date no one has mentioned it.

I feel it is needed as it is possible for a Echo to have the same Tag name across
networks - it should not happen as people should be changing for this but . .

Vincent
--- Mageia Linux v7.1 X64/Mbse v1.0.7.21/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

On 15 Jun 2021 at 02:19p, Vincent Coen pondered and said...

At the moment I have NOT changed the ELIST.NA to include a new field (Network) at
the start of the line as I am still waiting for comments regarding this one - mostly to see if any one uses this file as input to any automated software that
would get upset by such a change. To date no one has mentioned it.

If it were me I would just generate separate NA files for each network. This allows for people to use them to import/setup with.

I feel it is needed as it is possible for a Echo to have the same Tag
name across
networks - it should not happen as people should be changing for this
but . .

You could create a 'master' NA file as you describe as well but I don't see
it being useful as a tool to quickly import echomail area tags into a BBS
given you're proposing adding an extra field to each line.
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)