usage record for a part in nodelist

[amoners]

We may create a table to track usage record of a part.

A basic design like below:

-- 1. create a table A to record usage record of a part. have such attributes.
----- 1.1 S/N (foreign key from part)
----- 1.2 recorder
----- 1.3 action
----- 1.4 status
----- 1.5 status
----- 1.6 date
-- 2. add a link to a part and point to page B.
-- 3. page B: query databases and show the usage record in a page. The SQL sentence may like this 'select * from A where S/N='SFP20151111' order by time', like 'allParts.php'
--4 . page C: use this page to add each operation of a part like 'edit/addPart.php'

so we can track a part like an express smoothly.

[lingu]

(11-11-2015 10:28 AM)amoners Wrote:  We may create a table to track usage record of a part.

A basic design like below:

-- 1. create a table A to record usage record of a part. have such attributes.
----- 1.1 S/N (foreign key from part)
----- 1.2 recorder
----- 1.3 action
----- 1.4 status
----- 1.5 status
----- 1.6 date
-- 2. add a link to a part and point to page B.
-- 3. page B: query databases and show the usage record in a page. The SQL sentence may like this 'select * from A where S/N='SFP20151111' order by time'

so we can track a part like an express smoothly.

What is the use case for this function?

I thought we just needed to add a MSN (Manufacturer S/N) for searching a particular item with the MSN.

The usage info is currently handled by associating a component (e.g, a RAM module) to another (e.g., a server).

If we want to track the usage of the handling of the item, we can add notes to the 'note' attribute, or write records on TaB and add the link to the TaB thread to the 'note' attribute.

So I am not sure why we need to create a new table. What is the use case that motivated this, and why can't it be handled with the scheme I outlined above?

[amoners]

(11-11-2015 10:42 AM)lingu Wrote:  What is the use case for this function?

Tracking a part in details in nodelist, like shipping gene data to NB.

Quote:I thought we just needed to add a MSN (Manufacturer S/N) for searching a particular item with the MSN.

The usage info is currently handled by associating a component (e.g, a RAM module) to another (e.g., a server).

If we want to track the usage of the handling of the item, we can add notes to the 'note' attribute, or write records on TaB and add the link to the TaB thread to the 'note' attribute.

So I am not sure why we need to create a new table. What is the use case that motivated this, and why can't it be handled with the scheme I outlined above?

Here, I assumed the info should be recorded in nodelist. I thought the usage of nodelist is manage and track a part, so such info should be record in nodelist. It will be difficult to brows if we record most of info in Note attribute.

[lingu]

(11-11-2015 10:48 AM)amoners Wrote:  Here, I assumed the info should be recorded in nodelist. I thought the usage of nodelist is manage and track a part, so such info should be record in nodelist. It will be difficult to brows if we record most of info in Note attribute.

It's not a huge pain. Let's tolerate it and just use the 'note' attribute.

An important feature is to prevent mis-editing that erases all info in 'note'. Let's handle this with recording the web server log. If the erasure happens, we can see what was deleted, and who deleted it. The log is what we need to set up any way, and can be useful as data source for our own development of log analysis in the future.