Hello All!

Just to let you all know that as the elist system is receiving submissions from other nets i.e., other than Fido the reporting of all of them only occurs quarterly.

This is not a good idea so I can produce the three reports to show all in the system in tag name order OR in tag name within network order OR
Produce a similar three file set for each network where the network name is added to the existing file names such as ELIST-FSX.RPT, .NA, NO. with these file placed in their own archive named say ELISTFSXYYMM.ZIP.


Any one has any opinions on these ideas ?

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

Vincent Coen wrote to All <=-

Just to let you all know that as the elist system is receiving submissions from other nets i.e., other than Fido the reporting
of all of them only occurs quarterly.

This is not a good idea so I can produce the three reports to
show all in the system in tag name order OR in tag name within
network order OR Produce a similar three file set for each
network where the network name is added to the existing file
names such as ELIST-FSX.RPT, .NA, NO. with these file placed in
their own archive named say ELISTFSXYYMM.ZIP.

Any one has any opinions on these ideas ?

I think the third option would not be good, because many
systems/softwares do not handle long filenames properly. Should
probably stick with the 8.3 format.

I'd say the "tag name within network" order would be best.



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.14-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)

On 06-06-21 19:28, Dan Clough <=-
spoke to Vincent Coen about Re: Elist process future <=-

I think the third option would not be good, because many systems/softwares do not handle long filenames properly. Should
probably stick with the 8.3 format.

I'd say the "tag name within network" order would be best.

What he said.

Dale Shipp
fido_261_1466 (at) verizon (dot) net
(1:261/1466)


... Shipwrecked in Silver Spring, Maryland. 00:23:44, 07 Jun 2021
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)

Re: Elist process future function change
By: Vincent Coen to All on Sun Jun 06 2021 17:02:26

the system in tag name order OR in tag name within network order OR

I'd like to see "Tag name within Network" if at all possible.
JD
===
* El Gato de Fuego * 4:92/69 (FidoNet) * Pedasi, Panama


John

... After two days in hospital, I took a turn for the nurse.
--- SBBSecho 3.14-Win32
* Origin: El Gato de Fuego - Pedasi, Panama (4:920/69)

Hello Dan!

Sunday June 06 2021 19:28, you wrote to me:

Vincent Coen wrote to All <=-

Just to let you all know that as the elist system is receiving
submissions from other nets i.e., other than Fido the reporting
of all of them only occurs quarterly.

This is not a good idea so I can produce the three reports to
show all in the system in tag name order OR in tag name within
network order OR Produce a similar three file set for each
network where the network name is added to the existing file
names such as ELIST-FSX.RPT, .NA, NO. with these file placed in
their own archive named say ELISTFSXYYMM.ZIP.

Any one has any opinions on these ideas ?

I think the third option would not be good, because many
systems/softwares do not handle long filenames properly. Should
probably stick with the 8.3 format.

I'd say the "tag name within network" order would be best.

Yep, was thinking that as well so thats what I will do over the next few hours/days as need to check the code and what changes are needed.



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